ZeppelinApplication · Apache
CVE-2019-10095
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 · uneditedbash command injection vulnerability in Apache Zeppelin allows an attacker to inject system commands into Spark interpreter settings. This issue affects Apache Zeppelin Apache Zeppelin version 0.9.0 and prior versions.
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 · moderate confidenceA bash command injection vulnerability in Apache Zeppelin versions 0.9.0 and prior allows authenticated or unauthenticated attackers to inject and execute arbitrary system commands through Spark interpreter settings, potentially leading to full system compromise.
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
ZeppelinApplication
<= 0.9.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify Apache Zeppelin installation and versionLocate Zeppelin installation directory and check the version. Common locations: /opt/zeppelin, /usr/local/zeppelin, or check pom.xml if built from source. Run: find / -name 'zeppelin-server*.jar' 2>/dev/null or check a known version file if it exists in your deploymentAffected if Apache Zeppelin version is 0.9.0 or lower, or if you cannot confirm the version is higher than 0.9.0
-
Verify Spark interpreter is enabledCheck Zeppelin interpreter configuration. Typically found in interpreter.json or through the Zeppelin UI at Interpreter settings page. Look for 'spark' interpreter entry with 'enabled' status set to trueAffected if The Spark interpreter is enabled and configured in your Zeppelin deployment
-
Confirm network accessibility of Zeppelin UICheck if Zeppelin web interface is exposed to untrusted networks. Review firewall rules, reverse proxy configuration, or cloud security groups allowing access to Zeppelin port (default 8080). Run: netstat -tlnp | grep -E '8080|8081' or review your reverse proxy/load balancer configurationAffected if Zeppelin UI is accessible from networks where untrusted users exist, regardless of authentication being enabled
-
Check authentication configurationReview Zeppelin security settings in shiro.ini or equivalent configuration file. Verify whether anonymous access is permitted or if authentication is enforced for interpreter configuration pagesAffected if Anonymous access is allowed OR if authentication is enabled but weak/default credentials may be in use, allowing authenticated attackers to reach interpreter settings
Your environment is affected if you run Apache Zeppelin version 0.9.0 or lower with the Spark interpreter enabled and the Zeppelin interface accessible to potential attackers, regardless of authentication status.
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 Apache Zeppelin to a version that addresses this vulnerability, or implement network-level access controls to restrict who can access the Zeppelin interface and configure interpreter settings.
Fix this in Zeppelin
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10095 — 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-10095 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