dbcve.org
MongoDBDatabase / datastore · Jenkins

CVE-2020-2268

HIGH · 8.8 CVSS v3.1 Published 2020-09-16
Fix available
A fix is available. Upgrade to after 1.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A cross-site request forgery (CSRF) vulnerability in Jenkins MongoDB Plugin 1.3 and earlier allows attackers to gain access to some metadata of any arbitrary files on the Jenkins controller.

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

A CSRF vulnerability in Jenkins MongoDB Plugin 1.3 and earlier allows remote attackers to make authenticated requests on behalf of an administrator without proper token validation. The flaw enables unauthorized access to metadata of arbitrary files on the Jenkins controller file system.

MitigationUpgrade Jenkins MongoDB Plugin to version 1.4 or later which includes CSRF token protection for the affected endpoints.

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
MongoDBDatabase / datastore
Affected:<= 1.3

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

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

  1. Verify MongoDB plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'MongoDB', or check the $JENKINS_HOME/plugins directory for mongo* files.
    Affected if The MongoDB plugin appears in the list of installed plugins.
  2. Check MongoDB plugin version
    In the Installed plugins tab, find the MongoDB Plugin entry and note the version number displayed in the Version column. Alternatively, inspect the plugin's manifest file (META-INF/MANIFEST.MF) inside the plugin's .hpi file.
    Affected if The installed version is 1.3 or any version lower than 1.3 (e.g., 1.2, 1.1, 1.0).
  3. Confirm plugin is enabled and active
    In Jenkins, go to Manage Jenkins > Configure System and look for the MongoDB configuration section. Verify the plugin configuration is present and not disabled.
    Affected if The MongoDB plugin configuration section exists and the plugin is not explicitly disabled.

You are affected if the MongoDB Plugin version 1.3 or earlier is installed and the plugin is enabled in your Jenkins instance.

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 1.3
Interim mitigation

Upgrade Jenkins MongoDB Plugin to version 1.4 or later which includes CSRF token protection for the affected endpoints.

Fix this in MongoDB Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2268 — 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-2268 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