CVE-2017-9167
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 · uneditedlibautotrace.a in AutoTrace 0.31.1 has a heap-based buffer overflow in the ReadImage function in input-bmp.c:337:25.
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 confidenceA heap-based buffer overflow vulnerability exists in the ReadImage function within input-bmp.c of libautotrace.a version 0.31.1. The overflow occurs during BMP image parsing when the code fails to properly validate buffer sizes before writing data to the heap, potentially allowing remote code execution or denial of service via specially crafted BMP files.
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= 0.31.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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.
-
Check if AutoTrace is installedRun 'autotrace --version' or check for the autotrace binary in common paths (/usr/bin/autotrace, /usr/local/bin/autotrace)Affected if AutoTrace version 0.31.1 is returned by --version or found on the system
-
Verify the exact version numberCompare the installed version output to '0.31.1' - this specific version is the only one listed as affected in the CVEAffected if The installed version is exactly 0.31.1 (other versions are not listed as affected)
-
Confirm libautotrace.a library presenceSearch for libautotrace.a in standard library directories (find /usr -name 'libautotrace.a' 2>/dev/null)Affected if libautotrace.a version 0.31.1 exists on the system
-
Check for BMP input processing usageReview application logs, scripts, or user workflows that process BMP image files using AutoTrace or linked librariesAffected if BMP files are being processed by AutoTrace or an application linking against the vulnerable libautotrace.a library
-
Inspect input-bmp.c usageIf you have source code or a custom build, verify that input-bmp.c is included and the ReadImage function is invoked during BMP parsingAffected if The ReadImage function from input-bmp.c is used to parse BMP files with this version of the library
A system is affected only if AutoTrace version 0.31.1 is installed AND BMP image files are being processed using the vulnerable ReadImage function in libautotrace.a.
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 AutoTrace that addresses the buffer overflow in input-bmp.c, or implement proper bounds checking in the ReadImage function before processing BMP input data.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9167 — 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-9167 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