ZeppelinApplication · Apache
CVE-2017-12619
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.7.3 was vulnerable to session fixation which allowed an attacker to hijack a valid user session. Issue was reported by "stone lone".
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 confidenceApache Zeppelin versions prior to 0.7.3 contain a session fixation vulnerability that allows an attacker to set or fix a user's session ID before authentication, then hijack the legitimate user's session after they log in.
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.7.3CVSS 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
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 Apache Zeppelin is installedLook for Zeppelin installation directories or running processes. Common locations include /opt/zeppelin, /usr/local/zeppelin, or the directory where Zeppelin was extracted. Alternatively, check for running java processes with 'zeppelin' in the command line.Affected if Apache Zeppelin is present on the system
-
Determine the installed Zeppelin versionLocate the version file typically found in the Zeppelin home directory as 'zeppelin-version' or 'VERSION', or check the startup logs for the version number. The web interface may also display the version on the About page.Affected if The version cannot be determined or is older than 0.7.3
-
Compare the installed version against the affected rangeRead the version number found in the previous step and compare it numerically to 0.7.3. Any version prior to 0.7.3 (including 0.7.2, 0.7.1, 0.7.0, 0.6.x, 0.5.x and earlier) is within the affected range.Affected if The installed version is less than 0.7.3
-
Confirm Zeppelin authentication is enabledCheck the Zeppelin configuration file (typically zeppelin-site.xml or shiro.ini) for authentication settings. Verify that either Shiro authentication or another authentication mechanism is configured and active.Affected if Authentication is enabled and the version is below 0.7.3
A user is affected if Apache Zeppelin is running with a version lower than 0.7.3 and user authentication is enabled, as this creates the conditions for session fixation to occur during the login process.
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.7.3
Upgrade Apache Zeppelin to version 0.7.3 or later, which should contain the fix for session regeneration on authentication.
Fix this in Zeppelin
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12619 — 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-2017-12619 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