Repository ConnectorApplication · Jenkins
CVE-2020-2149
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 Repository Connector Plugin 1.2.6 and earlier transmits configured credentials in plain text as part of its global Jenkins configuration form, potentially resulting in their exposure.
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 Repository Connector Plugin versions 1.2.6 and earlier transmits credentials in plain text as part of the global Jenkins configuration form submission, allowing attackers to intercept and obtain credentials through network sniffing or man-in-the-middle 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
Repository ConnectorApplication
<= 1.2.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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Repository Connector Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or check the $JENKINS_HOME/plugins directory for repository-connector.jpi. Use the CLI command: java -jar jenkins-cli.jar -s http://localhost:8080/ list-plugins 2>/dev/null | grep -i repositoryAffected if The plugin appears in the list of installed plugins
-
Determine the installed plugin versionOn the Installed plugins page, find the Repository Connector entry and note the Version column. Alternatively, inspect the plugin manifest: unzip -p $JENKINS_HOME/plugins/repository-connector.jpi META-INF/MANIFEST.MF | grep Implementation-VersionAffected if Version is 1.2.6 or earlier (or the version cannot be determined, indicating an unpatched installation)
-
Check if credentials are configured for the pluginNavigate to Manage Jenkins > Configure System and look for the Repository Connector configuration section. Inspect whether any repository URLs, username/password credentials, or SSH credentials are configured there.Affected if Credentials (username/password, SSH keys, or other secrets) are stored or transmitted through the plugin configuration
You are affected if the Repository Connector Plugin version is 1.2.6 or earlier AND credentials are configured for use with the plugin, as these would be transmitted in plain text during configuration form submission.
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 dataUpgrade the Repository Connector Plugin to version 1.2.7 or later which addresses the credential exposure. Additionally, rotate any credentials that may have been transmitted through the vulnerable plugin.
Fix this in Repository Connector
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2149 — 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-2149 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