Incorrect permission checks in Jenkins Support Core Plugin

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2022-45383: 0.72% estimated exploitation activity in the next 30 days; percentile 53.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.v14049fabd860 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.v9b7a1d48db0f deprecates the Support/DownloadBundle permission. The Overall/Administer permission is now required to download support bundles.

Published by the source

16 Nov 2022, 12:00 UTC

Last modified by the source

5 Jan 2024, 17:12 UTC

Source last checked

26 Oct 2026, 16:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w2j3-pq63-339w

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-45383

Advisory: Incorrect permission checks in Jenkins Support Core Plugin
IDs: CVE-2022-45383, GHSA-w2j3-pq63-339w
Record: https://patchnext.com/advisories/cve-2022-45383 (revision 1, source checked 26 Oct 2026, 16:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins:support-core 1206.1208.v9b_7a_1d48db_0f. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:support-core: affected <= 1206.v14049fa; fixed in 1206.1208.v9b_7a_1d48db_0f

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:support-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jenkins-ci.plugins:support-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w2j3-pq63-339w (GitHub-reviewed advisory GHSA-w2j3-pq63-339w lists affected ranges: Maven org.jenkins-ci.plugins:support-core >=0 <=1206.v14049fa)

Commands are suggestions: review each one before running it.