Audit TrailApplication · Jenkins
CVE-2020-2287
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 · uneditedJenkins Audit Trail Plugin 3.6 and earlier applies pattern matching to a different representation of request URL paths than the Stapler web framework uses for dispatching requests, which allows attackers to craft URLs that bypass request logging of any target URL.
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 confidenceThe Jenkins Audit Trail Plugin 3.6 and earlier uses a different URL representation for pattern matching than the Stapler web framework uses for actual request dispatch. This discrepancy allows attackers to craft specially constructed URLs that bypass the plugin's request logging entirely, enabling malicious activity to go unrecorded in audit trails.
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
Audit TrailApplication
<= 3.6CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
-
Identify Audit Trail plugin installation statusIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugin directory (typically $JENKINS_HOME/plugins/audit-trail/). Use CLI: java -jar jenkins-cli.jar -s http://localhost:8080/ list-plugins | grep -i auditAffected if The plugin is listed as installed and the version is 3.6 or earlier
-
Determine the exact plugin versionCheck the plugin's manifest file: $JENKINS_HOME/plugins/audit-trail/META-INF/MANIFEST.MF for the Implementation-Version, or view the plugin details in the Jenkins plugin manager UIAffected if The Implementation-Version field shows 3.6 or any version lower than 3.7
-
Verify audit trail configuration is activeNavigate to Manage Jenkins > Configure System > Audit Trail (or the configured location for the plugin), or inspect the Jenkins configuration XML at $JENKINS_HOME/config.xml for <auditTrail> entriesAffected if Audit trail logging is configured and enabled with a log storage destination (file, logger, etc.)
-
Test for URL bypass vulnerabilitySend a request with encoded or specially crafted characters in the URL path (e.g., /job/test//job/other or with encoded slashes) and verify whether the request appears in the audit log. Compare the URL seen by Stapler (actual dispatch) versus the plugin's logging patternAffected if Requests with manipulated URL paths do NOT appear in the audit trail despite being successfully processed by Jenkins
The environment is affected if the Jenkins Audit Trail plugin version 3.6 or earlier is installed, the plugin is enabled, and specially crafted URLs can bypass audit logging.
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 Audit Trail Plugin to version 3.7 or later, which addresses the URL representation mismatch. If immediate update is not possible, implement supplementary request logging at the web server or proxy level as a compensating control.
Fix this in Audit Trail
Scoped from the published advisory
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2287 — 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-2020-2287 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