MavenApplication · Jenkins
CVE-2019-16550
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 a connection test form method in Jenkins Maven Release Plugin 0.16.1 and earlier allows attackers to have Jenkins connect to an attacker specified web server and parse XML documents.
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 Jenkins Maven Release Plugin where the connection test form lacks anti-CSRF protection. An attacker can trick authenticated Jenkins users into submitting malicious requests that cause the Jenkins server to connect to attacker-controlled servers and parse XML documents, potentially enabling XXE attacks or SSRF to internal services.
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
MavenApplication
<= 0.16.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.
-
Confirm Jenkins Maven Release Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed, or check for the presence of the maven-release-plugin folder in $JENKINS_HOME/plugins/Affected if The plugin appears in the installed plugins list or its directory exists in the plugins folder
-
Identify the installed plugin versionIn the Jenkins plugin manager Installed tab, locate the Version column for Maven Release Plugin; alternatively, examine the plugin's META-INF/MANIFEST.MF file inside $JENKINS_HOME/plugins/maven-release-plugin/Affected if A version number is displayed or readable from the manifest file
-
Compare version against the affected rangeCompare the installed version number to 0.16.1 - versions 0.16.1 and lower are affectedAffected if The installed version is 0.16.1 or any earlier version (e.g., 0.16.0, 0.15.0)
-
Verify the connection test functionality is accessibleLocate the Maven Release Plugin configuration page in Jenkins (typically under Manage Jenkins or project configuration) where the connection test form existsAffected if Users with configure permissions can access the connection test form
A user is affected if the Jenkins Maven Release Plugin is installed with version 0.16.1 or lower and the connection test functionality is accessible to authenticated users.
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 Jenkins Maven Release Plugin to a version newer than 0.16.1 that includes CSRF protection for the connection test form. If no update is available, disable or restrict access to the affected functionality.
Fix this in Maven
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16550 — 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-16550 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