Reverse Proxy AuthApplication · Jenkins
CVE-2023-32987
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins Reverse Proxy Auth Plugin 1.7.4 and earlier allows attackers to connect to an attacker-specified LDAP server using attacker-specified credentials.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA cross-site request forgery (CSRF) vulnerability in Jenkins Reverse Proxy Auth Plugin version 1.7.4 and earlier allows authenticated or unauthenticated attackers to trick administrators into making the Jenkins server connect to an attacker-specified LDAP server using attacker-specified credentials. This enables man-in-the-middle attacks on LDAP authentication traffic.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Reverse Proxy AuthApplication
<= 1.7.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Jenkins Reverse Proxy Auth Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Reverse Proxy Auth' or check the plugin directory $JENKINS_HOME/plugins for reverse-proxy-auth-pluginAffected if The plugin is present in the plugin list or filesystem
-
Check the installed plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed, find Reverse Proxy Auth Plugin and note the version number. Alternatively, inspect the plugin's manifest file at $JENKINS_HOME/plugins/reverse-proxy-auth-plugin/META-INF/MANIFEST.MFAffected if The version is 1.7.4 or earlier
-
Confirm Reverse Proxy Auth is enabledNavigate to Manage Jenkins > Configure Global Security > Authorization section, or check $JENKINS_HOME/config.xml for <useSecurity>true</useSecurity> and review if Reverse Proxy Auth realm is configured under Security RealmAffected if Reverse Proxy Auth is set as the Security Realm (authentication method)
-
Inspect LDAP server configurationReview the Reverse Proxy Auth plugin configuration at Manage Jenkins > Configure Global Security > Reverse Proxy Auth settings, or examine $JENKINS_HOME/org.jenkinsci.plugins.reverse_proxy_auth.ReverseProxySecurityRealm.xml if it existsAffected if The LDAP server host points to an unexpected or untrusted server, or contains credentials not provisioned by your organization
You are affected if the Reverse Proxy Auth Plugin version is 1.7.4 or earlier AND the plugin is enabled as the Security Realm with an LDAP configuration that could have been modified by an attacker.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Jenkins Reverse Proxy Auth Plugin to a version newer than 1.7.4. Review LDAP authentication configurations after updating to ensure no unauthorized server connections were made.
Fix this in Reverse Proxy Auth
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32987 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-32987 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data