AtlasApplication · Apache
CVE-2019-10070
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.8.3 and 1.1.0 were found vulnerable to Stored Cross-Site Scripting 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 · high confidenceApache Atlas versions 0.8.3 and 1.1.0 contain a stored Cross-Site Scripting vulnerability in the search functionality. Attackers can inject malicious JavaScript payloads through search input fields, which are persisted to the database and executed when other users view the search results or related pages.
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.8.3= 1.1.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 UI footer for the version number, or examine the pom.xml/build.xml file in the Atlas installation directory, or query the Atlas REST API endpoint /api/atlas/version if accessibleAffected if The installed version is 0.8.3 or 1.1.0 exactly
-
Confirm search feature is in useReview Atlas audit logs or access logs for requests to search-related endpoints such as /api/atlas/search or the Basic Search UI. Check if any users have performed searches in the systemAffected if Search functionality has been used and results are stored or displayed to multiple users
-
Inspect stored search data for malicious payloadsQuery the Atlas backend database (typically JanusGraph or Apache Solr depending on configuration) for stored search queries containing script tags, javascript:, or HTML event handlers in the search index or related tablesAffected if Stored search queries contain unsanitized script tags or XSS payloads that would execute when viewed by other users
-
Review HTTP response headersCapture a response from the Atlas search UI and examine if Content-Security-Policy headers are present and properly configured to block inline script executionAffected if CSP headers are absent or weak, allowing inline script execution from stored XSS payloads
A user is affected if Apache Atlas version 0.8.3 or 1.1.0 is installed, the search feature is accessible to users, and stored search queries with unsanitized script content exist in the system that could execute in other users' browsers.
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 Apache Atlas to a version that includes the security patch for this vulnerability. As a compensating control, implement robust input validation and output encoding on all search functionality, and consider deploying Content Security Policy headers to mitigate XSS execution.
Fix this in Atlas
Scoped from the published advisory
- Consultation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10070 — 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-2019-10070 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