ZeppelinApplication · Apache
CVE-2018-1328
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 · uneditedApache Zeppelin prior to 0.8.0 had a stored XSS issue via Note permissions. Issue reported by "Josna Joseph".
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 confidenceApache Zeppelin versions prior to 0.8.0 contain a stored cross-site scripting (XSS) vulnerability in the Note permissions functionality. Attackers can inject malicious scripts into note permission settings that persist on the server and execute when other users access those permissions.
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.8.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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify Apache Zeppelin installation and versionLocate the Zeppelin installation directory and check the version file or launch the application and verify the version displayed in the UI. Common locations include /usr/local/zeppelin, /opt/zeppelin, or the service start-up output.Affected if The installed version is any release prior to 0.8.0 (e.g., 0.7.x, 0.6.x, etc.)
-
Verify Note permissions feature is accessibleLog into the Zeppelin web interface and navigate to the Note management section. Access the permissions settings for any existing notebook by opening the note and locating the permissions or sharing configuration panel.Affected if The Note permissions functionality is available and configurable in the environment
-
Inspect stored permission settings for script contentReview all note permission configurations in the Zeppelin notebook metadata or database. Look for permission fields such as owner, readers, or writers that may contain HTML, JavaScript, or other scriptable content. Query the notebook metadata storage (typically in the notebook repository) for any unexpected characters like <script>, javascript:, onload, or other XSS vectors.Affected if Any permission setting contains persisted script tags or event handlers (e.g., <script>alert(1)</script> in an owner or reader field)
-
Check recent permission modification historyReview Zeppelin logs or audit trails for recent changes to note permissions. Look for patterns of permission modifications that coincide with unauthorized access or suspicious activity.Affected if Permission settings were recently modified and contain unexpected script content
You are affected if Apache Zeppelin version is below 0.8.0 and note permission settings contain or have contained persisted script content that could execute when users access those permissions.
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 data0.8.0
Upgrade Apache Zeppelin to version 0.8.0 or later to remediate this vulnerability. Additionally, implement input validation and output encoding for all user-supplied data in permission settings.
Fix this in Zeppelin
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1328 — 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-2018-1328 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