JenkinsApplication
CVE-2018-1999042
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 vulnerability exists in Jenkins 2.137 and earlier, 2.121.2 and earlier in XStream2.java that allows attackers to have Jenkins resolve a domain name when deserializing an instance of java.net.URL.
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 deserialization vulnerability in Jenkins' XStream library where the deserialization of java.net.URL objects triggers DNS resolution or HTTP connections to the specified URL. An attacker can exploit this to make the Jenkins server perform requests to arbitrary domains, potentially leading to Server-Side Request Forgery (SSRF) or internal network reconnaissance.
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
JenkinsApplication
<= 2.121.2<= 2.137CVSS 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.0/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.
-
Determine installed Jenkins versionNavigate to Manage Jenkins > About Jenkins in the web UI, or execute 'java -jar jenkins.war --version' from the command line on the serverAffected if Version is 2.121.2 or lower, or version 2.137 or lower (versions 2.122 through 2.136 are also affected if not patched)
-
Identify XStream-dependent pluginsReview installed plugins at Manage Jenkins > Manage Plugins; look for plugins that accept XML input or serialized Java objects, as these may use XStream for processingAffected if Plugins that deserialize XML or Java objects are installed and receive untrusted input
-
Audit XML configuration inputsSearch Jenkins configuration pages for fields that accept XML data; inspect any job configurations, config files, or API endpoints that accept XML payloadsAffected if Jenkins accepts XML data from untrusted sources that could contain serialized java.net.URL objects
-
Review network logs for anomalous requestsExamine Jenkins access logs and network traffic for unexpected outbound DNS resolutions or HTTP connections to arbitrary domains, especially those initiated by Jenkins processAffected if Jenkins is making outbound HTTP or DNS requests to unfamiliar external domains
You are affected if your Jenkins version is 2.137 or lower (specifically 2.121.2 or lower, or any version 2.122-2.136) and the instance processes untrusted XML data through XStream-based functionality.
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 Jenkins to version 2.138+, 2.122+, or later which contains the fix for this XStream deserialization issue. If immediate patching is not possible, consider network segmentation to limit Jenkins' ability to reach sensitive internal resources.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1999042 — 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-2018-1999042 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