AtlasApplication · Apache
CVE-2017-3150
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 use cookies that could be accessible to client-side script.
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 and 0.7.0 set cookies without the HttpOnly flag, allowing client-side scripts to potentially access sensitive session data. This XSS-adjacent vulnerability could enable attackers to steal authentication cookies via malicious scripts running in the user's browser.
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 versionCheck the Atlas version by examining the atlas-start.sh script, version.properties file, or running 'atlas_version' command if available in the installation directoryAffected if Version is exactly 0.6.0 or 0.7.0
-
Inspect HTTP response headers for cookie flagsLog into Atlas web UI and use browser developer tools (Network tab) or a tool like curl to capture HTTP response headers. Look for Set-Cookie headers and verify if the HttpOnly attribute is presentAffected if Set-Cookie headers do not include the HttpOnly attribute for session or authentication cookies
-
Check web application configuration for cookie settingsExamine the web.xml file in the Atlas web application deployment (typically in atlas/webapp/WEB-INF/web.xml) for session-config and cookie-config settingsAffected if The cookie-config element is missing or does not specify http-only=true
-
Review cookie-setting code pathsSearch Atlas source code or decompiled classes for javax.servlet.http.Cookie.setHttpOnly() calls or cookie creation patterns. Look in authentication-related servlets and filtersAffected if Cookies are created without calling setHttpOnly(true) or equivalent configuration
User is affected if running Apache Atlas version 0.6.0 or 0.7.0 AND the Set-Cookie responses from the Atlas web application do not include the HttpOnly attribute for session or authentication cookies.
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 dataConfigure cookies with the HttpOnly attribute to prevent JavaScript access. Review all cookie-setting code paths in the affected versions and apply the HttpOnly flag to session and authentication cookies.
Fix this in Atlas
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3150 — 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-3150 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