Crx Content Package DeployerApplication · Jenkins
CVE-2019-10437
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 cross-site request forgery vulnerability in Jenkins CRX Content Package Deployer Plugin 1.8.1 and earlier allowed attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
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 confidenceThis is a CSRF vulnerability in the Jenkins CRX Content Package Deployer Plugin (version 1.8.1 and earlier) that allows attackers to trigger Jenkins to connect to attacker-controlled URLs using credential IDs. By chaining this with another method to obtain valid credential IDs, attackers can capture and exfiltrate credentials stored in Jenkins.
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
Crx Content Package DeployerApplication
<= 1.8.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify if CRX Content Package Deployer plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'CRX Content Package Deployer' or check the plugin directory $JENKINS_HOME/plugins for a directory named 'crx-content-package-deployer'Affected if The plugin is listed as installed in Jenkins
-
Check the installed plugin versionIn Manage Jenkins > Manage Plugins > Installed, locate CRX Content Package Deployer and note the version number displayed in the plugin listAffected if The installed version is 1.8.1 or any version prior to 1.8.1
-
Verify the plugin is active and not disabledIn Manage Jenkins > Manage Plugins > Installed, ensure CRX Content Package Deployer shows as 'Enabled' or 'Active' status, and confirm it is not unchecked in the plugin managerAffected if The plugin is enabled and active in the Jenkins instance
-
Inspect for configured credentials used by the pluginNavigate to Manage Jenkins > Manage Credentials and review any credentials that may be associated with or used by the CRX Content Package Deployer plugin configurationAffected if Credentials are configured and accessible to the plugin, which could be exfiltrated via the CSRF vulnerability
A user is affected if the CRX Content Package Deployer plugin is installed, enabled, and running at version 1.8.1 or earlier while having credentials configured that could be targeted.
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 CRX Content Package Deployer Plugin to a version newer than 1.8.1. If immediate updating is not possible, disable the plugin until a patch can be applied.
Fix this in Crx Content Package Deployer
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-2019-10437 — 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-2019-10437 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