How severe is CVE-2022-45383?

CVE-2022-45383 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-45383?

CVE-2022-45383 affects the following packages: org.jenkins-ci.plugins:support-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-45383?

Update org.jenkins-ci.plugins:support-core to 1206.1208.v9b_7a_1d48db_0f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-45383 is resolved across your whole dependency graph.

How do I detect CVE-2022-45383 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:support-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-45383 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2022-45383 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-45383 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-45383?

CVE-2022-45383 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 54th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-45383?

CVE-2022-45383 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-45383 published, and has it been updated?

CVE-2022-45383 was published on November 15, 2022 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2022-45383 — support-core

MEDIUMFix: jenkinsci/support-core-plugin@9b7a1d4

CVE-2022-45383 is a medium-severity (CVSS 6.5) CWE-863 vulnerability in org.jenkins-ci.plugins:support-core. A fix is available for org.jenkins-ci.plugins:support-core — see the affected versions and patch details below.

Incorrect permission checks in Jenkins Support Core Plugin

Also known asGHSA-w2j3-pq63-339w

Published

Nov 15, 2022

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-45383.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:support-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Support Core Plugin 1206.v14049fa_b_d860 and earlier does not correctly perform permission checks in several HTTP endpoints.

This allows attackers with Support/DownloadBundle permission to download a previously created support bundle containing information limited to users with Overall/Administer permission.

Support Core Plugin 1206.1208.v9b_7a_1d48db_0f deprecates the Support/DownloadBundle permission. The Overall/Administer permission is now required to download support bundles.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:support-core`	all versions	1206.1208.v9b_7a_1d48db_0f`org.jenkins-ci.plugins:support-core:1206.1208.v9b_7a_1d48db_0f`

Affected Products

1 product · 1 configurations

Application

support corejenkins

< 1206.1208.v9b_7a_1d48db_0f

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:support-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:support-core to 1206.1208.v9b_7a_1d48db_0f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-45383 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Support Core Plugin defines the permission Support/DownloadBundle that allows users without Overall/Administer permission to create and download support bundles containing a limited set of diagnostic information. Support Core Plugin 1206.v14049fa_b_d860 and earlier does not correctly perform permission checks in several HTTP endpoints. This allows attackers with Support/DownloadBundle permission to download a previously created support bundle containing information limited to users with Overall/Administer permission. Support Core Plugin 1206.1208.v9b_7a_1d48db_0f deprecates the Support/Down

O3 Security · Impact-Aware SCA

Is CVE-2022-45383 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-863CWE-863

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Nov 15, 2022

Last updated

Oct 24, 2026

Identifiers

CVE-2022-45383

GHSA-w2j3-pq63-339w

References

Advisoryopenwall.com Advisoryjenkins.io · 2022 11 15 Advisorynvd.nist.gov · CVE 2022 45383 Webgithub.com · 9b7a1d48db0fdfb840ca3393e9462e687e69385b Packagegithub.com · support core plugin

Related vulnerabilities

Also affects support-core

This CVE is medium severity; 3 of 4 other CVEs affecting support-core are rated as high or higher (top: high).

CVE-2019-16540CVE-2021-21621CVE-2019-16539CVE-2022-25187

Same weakness: CWE-863

This CVE is medium severity; 4 of 4 other CVEs with CWE-863 are rated as high or higher (top: critical).

CVE-2026-114146CVE-2026-102943CVE-2026-95860CVE-2026-63198Browse all CWE-863

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2022-45383 — support-core

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-45383 in your dependencies?