SplunkApplication · Jenkins
CVE-2019-10390
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 sandbox bypass vulnerability in Jenkins Splunk Plugin 1.7.4 and earlier allowed attackers with Overall/Read permission to provide a Groovy script to an HTTP endpoint that can result in arbitrary code execution on the Jenkins master JVM.
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 Splunk Plugin before version 1.7.5 contains a sandbox bypass vulnerability that allows authenticated users with only Overall/Read permission to submit Groovy scripts to an HTTP endpoint, which then executes those scripts on the Jenkins master JVM without proper sandbox restrictions, achieving arbitrary code execution.
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
SplunkApplication
<= 1.7.4CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Splunk Plugin is installedIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Splunk' plugin, or check the plugin manifest file (splunk.jpi) in the JENKINS_HOME/plugins directoryAffected if The Splunk plugin appears in the installed plugins list
-
Check installed Splunk Plugin versionView the version number shown in the plugin list (Manage Jenkins > Manage Plugins > Installed), or read the META-INF/MANIFEST.MF file inside splunk.jpiAffected if The version listed is 1.7.4 or earlier (any version <= 1.7.4)
-
Confirm the vulnerable HTTP endpoint is accessibleCheck if the Splunk Plugin's HTTP endpoint is exposed by reviewing Jenkins configuration or network access settings; the endpoint accepts Groovy script submissionsAffected if The Splunk Plugin endpoint is reachable over the network without additional access controls
-
Identify users with Overall/Read permissionGo to Manage Jenkins > Manage Users or check authorization matrix in Manage Jenkins > Configure Global Security, and review which users or groups have Overall/Read permissionAffected if There are users with Overall/Read permission who should not have elevated access, as this permission level is sufficient to exploit the flaw
You are affected if the Splunk Plugin is installed at version 1.7.4 or earlier and the HTTP endpoint is accessible to users with Overall/Read permission.
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 Splunk Plugin to version 1.7.5 or later to receive the sandbox fix. As a temporary measure, restrict network access to the affected HTTP endpoint or revoke Overall/Read permission from untrusted users until the upgrade can be applied.
Fix this in Splunk
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10390 — 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-10390 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