DatabaseDatabase / datastore · Jenkins
CVE-2020-2242
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 missing permission check in Jenkins database Plugin 1.6 and earlier allows attackers with Overall/Read access to Jenkins to connect to an attacker-specified database 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 confidenceThe Jenkins database Plugin versions 1.6 and earlier lacks proper permission checks in database connection functionality. An attacker with basic Overall/Read access (the lowest privilege level in Jenkins) can configure the plugin to connect to an attacker-controlled database server using attacker-specified credentials, potentially exfiltrating data or conducting further attacks.
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
DatabaseDatabase / datastore
<= 1.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Verify if Jenkins Database Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'database', or check the $JENKINS_HOME/plugins directory for the database plugin folder.Affected if The database plugin is present in the installed plugins list.
-
Check the installed version of the Database PluginIn Manage Jenkins > Manage Plugins > Installed, find the Database Plugin and note the Version column. Alternatively, check the version file in $JENKINS_HOME/plugins/database.jpi or database folder.Affected if The version is 1.6 or earlier.
-
Verify access to database connection configurationNavigate to Manage Jenkins > Configure System and look for the Database configuration section. Attempt to access or view database connection settings.Affected if Users with Overall/Read permission can access or view the database connection configuration page.
-
Review existing database connection configurationsIn the Database Plugin configuration section, examine any configured database connections for hostnames, ports, and credentials that may be unauthorized or pointing to unexpected servers.Affected if There are database connections configured to servers you do not recognize or did not authorize.
Your environment is affected if the Database Plugin is installed with version 1.6 or earlier and users with basic Overall/Read access can access the database connection configuration without elevated permissions.
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 the Jenkins database Plugin to version 1.7 or later, which includes the missing permission check. Review database connection configurations to ensure no unauthorized connections were made.
Fix this in Database
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-2020-2242 — 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-2242 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