CVE-2017-12619 json
Session Fixation in Apache Zeppelin
published 2019-04-23 7 y ago modified 2026-06-17 4 mo ago also GHSA-c538-924g-99q4 , EUVD-2019-0415
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.9%
- EPSS 4.9% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
Apache 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".
Patch / fix
- maven org.apache.zeppelin:zeppelin 0.7.3
- apache zeppelin 0.7.3
Exploit prediction
4.95% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
| GitHub | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.zeppelin:zeppelin | <0.7.3 |
0.7.3 |
Affected products
- Apache Software Foundation Apache Zeppelin
Classification
- Weakness
-
- CWE-384 Session Fixation
References
-
zeppelin.apache.org
/releases/zeppelin-release-0.7.3.html
web, release-notes, vendor-advisory
-
lists.apache.org
/thread.html/ff6b995a5a3ba8db4d6b14b4d9dd487e7bf2e3bdd5b375b64a25fd06%40%3Cusers.zeppelin.apache.org%3E
mailing-list
-
openwall.com
/lists/oss-security/2019/04/23/1
mailing-list, web, release-notes, third-party-advisory
-
securityfocus.com
/bid/108050
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-12619
advisory
-
lists.apache.org
/thread.html/ff6b995a5a3ba8db4d6b14b4d9dd487e7bf2e3bdd5b375b64a25fd06@%3Cusers.zeppelin.apache.org%3E
web
Sources
- CVE List CVE-2017-12619
- GitHub Advisory GHSA-c538-924g-99q4
- NVD CVE-2017-12619
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.