Crx Content Package DeployerApplication · Jenkins
CVE-2019-10438
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 CRX Content Package Deployer Plugin 1.8.1 and earlier allowed attackers with Overall/Read permission 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 confidenceThe CRX Content Package Deployer Plugin versions 1.8.1 and earlier lacked proper permission checks in endpoints that configure connections to external CRX/AEM repositories. Attackers with basic Overall/Read permission could specify arbitrary URLs and leverage credential IDs (obtained through other means) to capture stored credentials by forcing Jenkins to connect to attacker-controlled 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
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 CRX Content Package Deployer plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or inspect the plugin directory $JENKINS_HOME/plugins/crx-content-package-deployer/ for the presence of the plugin filesAffected if The plugin is present in the Jenkins environment
-
Check installed plugin versionInspect the plugin's MANIFEST.MF file in $JENKINS_HOME/plugins/crx-content-package-deployer/META-INF/MANIFEST.MF for the Bundle-Version attribute, or view the version via Manage Jenkins > Manage Plugins > InstalledAffected if Version is 1.8.1 or lower
-
Identify users with Overall/Read permissionReview Jenkins security realm and authorization matrix at Manage Jenkins > Configure Global Security to enumerate users or groups granted Overall/Read permissionAffected if Non-admin users or groups possess Overall/Read permission
-
Check for configured CRX/AEM repository credentialsInspect credentials configured in Jenkins at Manage Jenkins > Manage Credentials, specifically looking for any credentials stored for CRX or AEM repository connectionsAffected if CRX/AEM credentials exist in Jenkins credential store
-
Verify vulnerability exposure through configuration endpointsAttempt to access the CRX Content Package Deployer plugin configuration endpoints (typically under /plugin/crx-content-package-deployer/) using an account with only Overall/Read permission to confirm lack of permission enforcementAffected if Endpoints are accessible and permit configuration changes without Overall/Administer permission
User is affected if the CRX Content Package Deployer plugin version is 1.8.1 or lower AND non-admin users with Overall/Read permission can access plugin configuration endpoints or trigger outbound connections to arbitrary URLs.
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 CRX Content Package Deployer Plugin to version 1.8.2 or later which includes the missing permission check. Review credential storage and restrict Overall/Read access for non-admin users if not already done.
Fix this in Crx Content Package Deployer
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10438 — 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-10438 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