AtlasApplication · Apache
CVE-2017-3155
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 Atlas versions 0.6.0-incubating and 0.7.0-incubating were found vulnerable to cross frame scripting.
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 Atlas versions 0.6.0-incubating and 0.7.0-incubating contain a cross frame scripting (XFS) vulnerability that allows attackers to embed malicious frames within legitimate Atlas pages. This enables clickjacking attacks where users can be tricked into performing unintended actions.
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
AtlasApplication
= 0.6.0= 0.7.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 Atlas installation and versionLocate the Atlas installation directory and check the version file, or query the Atlas web API endpoint /api/atlas/admin/version if the service is runningAffected if The installed version is exactly 0.6.0-incubating or 0.7.0-incubating
-
Confirm Atlas web interface is accessibleAccess the Atlas web UI via browser or curl the main page (default port 21000)Affected if Atlas web interface responds and the version from step 1 is affected
-
Check for missing X-Frame-Options headerSend an HTTP request to the Atlas web application and inspect response headers: curl -I http://localhost:21000/ (or the actual Atlas host:port)Affected if The response headers do NOT include X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN
-
Check for missing Content-Security-Policy frame-ancestorsInspect the same HTTP response headers from step 3 for a Content-Security-Policy header that includes frame-ancestorsAffected if No Content-Security-Policy header is present, or it does not contain the frame-ancestors directive
You are affected if running exactly version 0.6.0-incubating or 0.7.0-incubating AND the HTTP responses from Atlas lack X-Frame-Options and CSP frame-ancestors headers, allowing the application to be embedded in iframes.
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 dataImplement X-Frame-Options: DENY or SAMEORIGIN header and/or Content-Security-Policy with frame-ancestors directive on the Apache Atlas web application to prevent the application from being embedded in iframes.
Fix this in Atlas
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3155 — 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-3155 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