AtlasApplication · Apache
CVE-2017-3153
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 Reflected XSS in the search functionality.
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 · moderate confidenceReflected XSS vulnerability in Apache Atlas versions 0.6.0-incubating and 0.7.0-incubating allows attackers to inject malicious scripts via the search functionality. User-supplied input is reflected back without proper sanitization, enabling script execution in victim browsers.
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 installed Atlas version by reviewing release documentation, startup logs, or the atlas-application.properties file. Look for version indicators such as '0.6.0' or '0.7.0' in the installation directory or build artifacts.Affected if The installed version is exactly 0.6.0-incubating or exactly 0.7.0-incubating.
-
Confirm web interface is accessibleVerify that the Apache Atlas web UI or REST API endpoints are exposed and reachable. This is typically on port 21000 by default. Attempt to access the login page or API health endpoint.Affected if The Atlas web interface is accessible over the network.
-
Verify search functionality is enabledCheck if the Atlas search feature is operational by logging into the web UI and attempting to use the search box, or by making a query request to the search API endpoint.Affected if The search functionality is available and accepts user input.
-
Inspect search request handlingReview the HTTP request and response when submitting search input. Look for reflected parameters in the response without sanitization. Check the server response headers and body for unencoded user input.Affected if User-supplied search query parameters are reflected back in the response without proper encoding or sanitization.
You are affected if Apache Atlas version 0.6.0-incubating or 0.7.0-incubating is installed AND the web-based search functionality is accessible and reflects user input without encoding.
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 dataUpgrade to Apache Atlas version 0.8.0-incubating or later. As a temporary measure, implement input validation and output encoding on all search parameters.
Fix this in Atlas
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3153 — 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-3153 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