dbcve.org
AtlasApplication · Apache

CVE-2017-3152

MEDIUM · 6.1 CVSS v3.0 Published 2017-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Apache Atlas versions 0.6.0-incubating and 0.7.0-incubating were found vulnerable to DOM XSS in the edit-tag 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 · high confidence

DOM-based XSS vulnerability in Apache Atlas versions 0.6.0-incubating and 0.7.0-incubating allows injection of malicious scripts through the edit-tag functionality. The vulnerability exists due to insufficient input sanitization when handling user-supplied data in the DOM.

MitigationUpgrade to a patched version of Apache Atlas or implement proper output encoding/sanitization in the edit-tag functionality to neutralize XSS vectors.

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
Affected:= 0.6.0= 0.7.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Atlas installation and version
    Check for Apache Atlas installation and determine the installed version using package manager, service information, or by querying the Atlas web interface/version endpoint
    Affected if The installed version is exactly 0.6.0-incubating or 0.7.0-incubating
  2. Verify edit-tag functionality is accessible
    Access the Apache Atlas web UI and navigate to the tag management section, specifically the edit-tag feature used for creating or modifying tags
    Affected if The edit-tag feature is accessible and operational in the Atlas web interface
  3. Confirm lack of input sanitization in edit-tag
    Inspect the edit-tag functionality by submitting test input with special characters (such as <script> tags or event handlers) and observing if these are rendered unescaped in subsequent page loads
    Affected if User-supplied input in the edit-tag field is reflected back into the page HTML 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 edit-tag functionality is accessible, as the DOM-based XSS exists when user input is not properly sanitized in this feature.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Apache Atlas or implement proper output encoding/sanitization in the edit-tag functionality to neutralize XSS vectors.

Fix this in Atlas Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3152 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-3152 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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