WarningsApplication · Jenkins
CVE-2019-1003007
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 exists in Jenkins Warnings Plugin 5.0.0 and earlier in src/main/java/hudson/plugins/warnings/GroovyParser.java that allows attackers to execute arbitrary code via a form validation HTTP endpoint.
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 confidenceA cross-site request forgery (CSRF) vulnerability in Jenkins Warnings Plugin 5.0.0 and earlier allows remote attackers to execute arbitrary code by tricking authenticated users into submitting malicious requests to the form validation endpoint in GroovyParser.java.
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
WarningsApplication
<= 5.0.0CVSS 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.0/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 Jenkins Warnings Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Warnings' or check the plugin directory $JENKINS_HOME/plugins for a folder named 'warnings'Affected if The Warnings plugin is present in the plugins directory or listed in the installed plugins
-
Identify the installed version of Jenkins Warnings PluginIn Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find the Warnings plugin and note the version number displayed in the 'Version' columnAffected if The installed version is 5.0.0 or any earlier version (e.g., 5.0.0, 4.0.0, 3.0.0, etc.)
-
Confirm the GroovyParser form validation endpoint is accessibleCheck if the Jenkins instance exposes the form validation API for the Warnings plugin. This is typically at /jenkins-root/descriptorByName/GroovyParser/validate or similar endpoint under the warnings plugin context. Access to this endpoint does not require explicit configuration as it is enabled by default in affected versionsAffected if The form validation endpoint exists and responds to requests without requiring CSRF crumb validation (the vulnerability condition)
-
Verify CSRF protection is not applied to the form validation endpointSubmit a test request to the GroovyParser form validation endpoint without a valid Jenkinscrumb (CSRF token) header. In affected versions, the request will succeed; in patched versions, it will be rejectedAffected if The endpoint accepts requests without a valid crumb (Jenkins-Crumb header or crumb= parameter)
A user is affected if the Jenkins Warnings Plugin is installed with version 5.0.0 or earlier AND the GroovyParser form validation endpoint is exposed without CSRF protection.
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 Warnings Plugin to a version newer than 5.0.0 that includes proper CSRF protection (crumb validation) on form validation endpoints.
Fix this in Warnings
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003007 — 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-1003007 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