CVE-2017-3154 json
Apache Atlas produces Stack trace in error response
published 2017-08-29 9 y ago modified 2026-06-17 4 mo ago also GHSA-fx92-wh72-8g9q , PYSEC-2017-110 , EUVD-2017-0010
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
Error responses from Apache Atlas versions 0.6.0-incubating and 0.7.0-incubating included stack trace, exposing excessive information.
Patch / fix
- maven org.apache.atlas:atlas-common 0.7.1-incubating
Exploit prediction
2.05% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| OSV | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.atlas:atlas-common | >=0.6.0-incubating, <0.7.1-incubating |
0.7.1-incubating |
| pypi | apache-atlas | all versions |
no fix listed |
Affected products
- Apache Software Foundation Apache Atlas
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
lists.apache.org
/thread.html/4a4fef91e067fd0d9da569e30867c1fa65e2a0520acde71ddefee0ea%40%3Cdev.atlas.apache.org%3E
mailing-list, web
-
securityfocus.com
/bid/100581
vdb-entry, web
-
nvd.nist.gov
/vuln/detail/CVE-2017-3154
advisory
-
github.com
/apache/atlas
package
-
github.com
/pypa/advisory-database/tree/main/vulns/apache-atlas/PYSEC-2017-110.yaml
web
-
lists.apache.org
/thread.html/4a4fef91e067fd0d9da569e30867c1fa65e2a0520acde71ddefee0ea@%3Cdev.atlas.apache.org%3E
web
Sources
- CVE List CVE-2017-3154
- GitHub Advisory GHSA-fx92-wh72-8g9q
- NVD CVE-2017-3154
- OSV PYSEC-2017-110
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.