AtlasApplication · Apache
CVE-2017-3151
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 Stored Cross-Site Scripting 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 · moderate confidenceStored Cross-Site Scripting vulnerability in Apache Atlas versions 0.6.0-incubating and 0.7.0-incubating allows attackers to inject malicious JavaScript payloads into the edit-tag functionality, which is then executed in the browsers of users who view the affected tags.
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.1/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 web interface footer for version number, or examine the atlas-application.properties file in the conf directory for property 'atlas.version', or check the pom.xml in the Atlas installation directoryAffected if Version is 0.6.0-incubating or 0.7.0-incubating
-
Confirm Atlas web UI is accessibleAttempt to access the Atlas web interface at the configured host and port (default typically http://localhost:21000) and verify the login page loadsAffected if Web interface is accessible and version is vulnerable
-
Check if tag classification feature is in useNavigate to the 'Tags' or 'Classification' section in the Atlas web UI and list existing tags defined in the systemAffected if Any tags exist in the system, the edit-tag functionality is being used
-
Inspect stored tag definitions for malicious contentUsing Atlas REST API, query all tag definitions: GET /api/atlas/types/typedef?type=TAG or view tags through the web UI and examine the tag names and attribute values for script tags, javascript: URLs, or event handlersAffected if Tag names or attributes contain unsanitized user-supplied content such as <script>, javascript:, or on* event handlers
-
Verify tag creation/edit capability is enabledCheck if the authenticated user has permission to create or edit tags through the web UI or API, as the vulnerability requires the edit-tag functionalityAffected if Users have tag edit permissions and the system uses vulnerable versions
You are affected if Apache Atlas version is 0.6.0-incubating or 0.7.0-incubating AND the tag classification feature is enabled and accessible through the web interface.
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 a patched version of Apache Atlas beyond 0.7.0-incubating; implement proper input validation and output encoding for all user-supplied content in tag fields.
Fix this in Atlas
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3151 — 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-3151 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