CVE-2022-45384 — reverse-proxy-auth-plugin
MEDIUMCVE-2022-45384 is a medium-severity (CVSS 6.5) CWE-522 vulnerability in org.jenkins-ci.main:reverse-proxy-auth-plugin. A fix is available for org.jenkins-ci.main:reverse-proxy-auth-plugin — see the affected versions and patch details below.
Jenkins Reverse Proxy Auth Plugin vulnerable due to plaintext storage of passwords
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-45384.
EPSS Exploitation Probability
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
org.jenkins-ci.main:reverse-proxy-auth-pluginReal-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
Jenkins Reverse Proxy Auth Plugin versions 1.7.3 and earlier stores the LDAP manager password unencrypted in the global config.xml file on the Jenkins controller where it can be viewed by attackers with access to the Jenkins controller file system.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.main:reverse-proxy-auth-plugin | ≥ 1.7.3&&< 1.7.4 | 1.7.4org.jenkins-ci.main:reverse-proxy-auth-plugin:1.7.4 |
Affected Products
reverse proxy authjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:reverse-proxy-auth-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:reverse-proxy-auth-plugin to 1.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-45384 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2022-45384 in your dependencies?
Find it across Maven, including transitive dependencies.