CVE-2022-38367: The Netic User Export add-on before 2.0.6 for Atlassian Jira does not perform authorization checks

Q: How do I fix CVE-2022-38367?

user export for jira: upgrade to 2.0.6. Exact commands for each OS are on this page.

Q: Is CVE-2022-38367 being exploited?

CVE-2022-38367 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-38367 affect?

CVE-2022-38367 affects user export for jira. Severity is medium (CVSS 5.3). The Netic User Export add-on before 2.0.6 for Atlassian Jira does not perform authorization checks. This might allow an unauthenticated user to export all users from Jira by making an HTTP request to the affected endpoint.

Q: How urgent is CVE-2022-38367?

Priority 34/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2022-38367 is a medium-severity flaw (CVSS 5.3) affecting user export for jira. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Netic User Export add-on before 2.0.6 for Atlassian Jira does not perform authorization checks. This might allow an unauthenticated user to export all users from Jira by making an HTTP request to the affected endpoint.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 57%)
CISA exploited list	No
Weakness	CWE-862
Published	2022-09-05
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: netic

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-09-05 18:15 UTCPublished CVE record published
2026-06-17 04:56 UTCUpdated Record last modified

netic user export for jira UPGRADE

Affected: < 2.0.6

Fixed in: 2.0.6

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy user-export-for-jira || rpm -q user-export-for-jira || user-export-for-jira --version

2. UPGRADE to 2.0.6 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade user-export-for-jira

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade user-export-for-jira

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-38367?

user export for jira: upgrade to 2.0.6. Exact commands for each OS are on this page.

Is CVE-2022-38367 being exploited?

CVE-2022-38367 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-38367 affect?

CVE-2022-38367 affects user export for jira. Severity is medium (CVSS 5.3). The Netic User Export add-on before 2.0.6 for Atlassian Jira does not perform authorization checks. This might allow an unauthenticated user to export all users from Jira by making an HTTP request to the affected endpoint.

How urgent is CVE-2022-38367?

Priority 34/100. Remotely exploitable, no login, no user action

Software pages

Atlassian Jira vulnerabilities

References

← Back to latest CVEs