CVE-2017-1000498
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 · uneditedAndroidSVG version 1.2.2 is vulnerable to XXE attacks in the SVG parsing component resulting in denial of service and possibly remote code execution
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 confidenceAndroidSVG version 1.2.2 contains an XML External Entity (XXE) vulnerability in its SVG parsing component. The library fails to properly disable external entity processing when parsing SVG files, allowing attackers to craft malicious SVG documents that can reference external resources, cause denial of service, or potentially execute arbitrary code.
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= 1.2.2CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 AndroidSVG library versionLocate the AndroidSVG library JAR file in your project dependencies (check build.gradle, pom.xml, or the libs folder) and note the version numberAffected if The version is 1.2.2 exactly
-
Verify SVG parsing usageSearch your codebase for imports of com.caverock.andsvg.SVG or SVG classes and identify where SVG.fromString() or SVG.fromInputStream() is called to parse SVG dataAffected if Your application parses SVG files using AndroidSVG
-
Check for XXE-safe XML parser configurationReview the SVG parsing code to determine if the underlying XML parser has DTDs and external entities explicitly disabled (look for features like DISABLE_DTD, DISABLE_EXTERNAL_ENTITY_RESOLUTION set to true)Affected if No XXE protection is configured in the XML parser used by AndroidSVG
-
Determine SVG input source trust levelIdentify whether SVG files parsed by AndroidSVG come from untrusted sources such as user uploads, external APIs, or network requestsAffected if AndroidSVG processes SVG from untrusted or external sources
You are affected if your application uses AndroidSVG version 1.2.2 to parse SVG files from untrusted sources without explicit XXE protection configured in the XML parser.
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 AndroidSVG to a patched version (1.3.0 or later) that disables external entity processing in the XML parser, or implement XXE protection by configuring the XML parser to disable DTDs and external entities before parsing any SVG input.
- Consultation3.0 h
- Implementation6.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 $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000498 — 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-1000498 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