NomadApplication · Jenkins
CVE-2019-1003092
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 Nomad Plugin in the NomadCloud.DescriptorImpl#doTestConnection form validation method allows attackers to initiate a connection to an attacker-specified server.
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 Jenkins Nomad Plugin has a CSRF vulnerability in the NomadCloud.DescriptorImpl#doTestConnection form validation method. An attacker can trick an authenticated Jenkins user into unknowingly initiating a connection to an attacker-controlled server by leveraging the lack of CSRF protection on this form validation endpoint.
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
NomadApplication
all versionsCVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Jenkins Nomad plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Nomad' or check the plugin directory $JENKINS_HOME/plugins for nomad plugin filesAffected if The Nomad plugin is installed (all versions are affected)
-
Check if Jenkins CSRF protection is enabledNavigate to Jenkins > Manage Jenkins > Configure Global Security > CSRF Protection section. Verify if 'Enable proxy compatibility' or default 'crumb' validation is enabledAffected if CSRF protection (crumb validation) is disabled or not configured in Jenkins global security settings
-
Inspect form validation endpoint configurationExamine the Jenkins CLI or API response when calling the doTestConnection endpoint at /descriptorByName/org.jenkinsci.plugins.nomad.NomadCloud/testConnection without providing a validcrumb tokenAffected if The endpoint accepts requests without requiring a valid CSRF crumb token (test with a simple curl request lacking the crumb)
-
Verify authentication and session requirementsReview Jenkins logs and network traffic when the form validation endpoint is accessed. Check whether an authenticated session and validcrumb are both requiredAffected if The doTestConnection endpoint can be triggered without both an authenticated session and a valid CSRF token
A user is affected if the Jenkins Nomad plugin is installed AND Jenkins CSRF protection (crumb validation) is disabled or the doTestConnection endpoint can be accessed without requiring a valid CSRF token.
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 dataEnable Jenkins built-in CSRF protection (crumb validation) and update the Nomad plugin to the latest version that includes proper CSRF token validation in the doTestConnection method.
Fix this in Nomad
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003092 — 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-1003092 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