dbcve.org
Audit TrailApplication · Jenkins

CVE-2020-2288

MEDIUM · 5.3 CVSS v3.1 Published 2020-10-08
Fix available
A fix is available. Upgrade to after 3.6 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
In Jenkins Audit Trail Plugin 3.6 and earlier, the default regular expression pattern could be bypassed in many cases by adding a suffix to the URL that would be ignored during request handling.

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 confidence

The Jenkins Audit Trail Plugin 3.6 and earlier uses a default regular expression pattern to match URLs for logging. This regex pattern can be bypassed by appending a suffix to the URL that the request handler ignores but the audit trail regex doesn't properly match, allowing certain requests to avoid being logged. This creates a security monitoring gap where unauthorized or sensitive actions may not be captured in audit logs.

MitigationUpdate Jenkins Audit Trail Plugin to version 3.7 or later where the regex bypass has been fixed. Review existing audit logs for any suspicious activity that may have occurred during the vulnerable period.

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
Affected:<= 3.6

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Audit Trail Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Audit Trail' in the list. Alternatively, check the file $JENKINS_HOME/plugins/audit-trail.jpi (or .hpi) exists.
    Affected if The plugin is not installed on the Jenkins instance.
  2. Check the installed version number
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, find Audit Trail Plugin and note the Version column. Compare this to the affected versions: 3.6 and earlier.
    Affected if The installed version is 3.6 or lower.
  3. Locate the audit trail configuration file
    Check for the presence of the configuration file at $JENKINS_HOME/org.jenkinsci.plugins.audit_trail.AuditTrailPlugin.xml or in the Jenkins script console run: Jenkins.instance.getPlugin("audit-trail") to confirm plugin object.
    Affected if Cannot locate plugin configuration indicates plugin may not be properly configured.
  4. Inspect the URL logging regex pattern
    Review the plugin configuration XML file or access via Jenkins > Manage Jenkins > Configure System > Audit Trail section. Look for the 'URL pattern' or 'Regular expression' field that defines which URLs are logged.
    Affected if The default regex pattern is in use (not customized) and matches the bypass condition where appended URL suffixes are not captured.
  5. Test regex bypass susceptibility
    If you have access to make test requests, append a non-standard suffix (such as /some/path;extra or /some/path%00null) to a Jenkins URL and verify whether the request appears in the audit trail logs.
    Affected if The request with bypass suffix does NOT appear in audit logs while the base URL request does appear.

A user is affected if the Jenkins Audit Trail Plugin version is 3.6 or earlier AND the default URL regex pattern is in use, allowing certain requests to bypass audit logging.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.6
Interim mitigation

Update Jenkins Audit Trail Plugin to version 3.7 or later where the regex bypass has been fixed. Review existing audit logs for any suspicious activity that may have occurred during the vulnerable period.

Fix this in Audit Trail Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-2288 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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