dbcve.org
AutotraceApplication · Autotrace Project

CVE-2017-9152

CRITICAL · 9.8 CVSS v3.0 Published 2017-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
libautotrace.a in AutoTrace 0.31.1 has a heap-based buffer over-read in the pnm_load_raw function in input-pnm.c:346:41.

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

Heap-based buffer over-read vulnerability in the pnm_load_raw function of libautotrace.a (AutoTrace 0.31.1). The function reads beyond allocated heap memory boundaries when processing PNM (portable anymap) image files, potentially allowing disclosure of sensitive heap contents or denial of service.

MitigationUpdate to a patched version of AutoTrace or implement bounds checking in pnm_load_raw to validate buffer indices before memory reads. Sanitize PNM input files before processing.

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
AutotraceApplication
Affected:= 0.31.1

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

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

  1. Confirm AutoTrace installation
    Run 'which autotrace' or check for /usr/bin/autotrace, and locate libautotrace.a using 'find / -name libautotrace.a 2>/dev/null'
    Affected if AutoTrace binary or libautotrace.a library is present on the system
  2. Determine installed version
    Run 'autotrace --version' or check the library version metadata
    Affected if Version is exactly 0.31.1
  3. Verify PNM input processing is used
    Inspect any automated workflows, scripts, or applications that call AutoTrace to see if they process .pnm, .ppm, .pgm, or .pbm file types
    Affected if PNM/PNB/PPM/PGM image files are being processed by AutoTrace
  4. Check for direct libautotrace.a usage
    Review application code or build configurations that link against libautotrace.a and process image inputs
    Affected if Custom applications link libautotrace.a and handle image file inputs

You are affected if AutoTrace version 0.31.1 is installed and actively processing PNM (portable anymap) image files through the pnm_load_raw function.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of AutoTrace or implement bounds checking in pnm_load_raw to validate buffer indices before memory reads. Sanitize PNM input files before processing.

Recommended fix Moderate confidence

Latest stable release from https://github.com/autotrace/autotrace (check releases for version newer than 0.31.1)

  1. 1. Check if your Linux distribution provides an updated autotrace package through its package manager (e.g., apt, yum, dnf, pacman)
  2. 2. If a newer package is available, update to it: 'sudo apt-get update && sudo apt-get upgrade autotrace' (or equivalent for your distribution)
  3. 3. If no updated package is available, download the latest source code from the official AutoTrace repository at https://github.com/autotrace/autotrace
  4. 4. Compile and install the latest version following the INSTALL or README instructions in the source distribution
  5. 5. Verify the installation by running 'autotrace --version' to confirm the new version is active
  6. 6. Test that your AutoTrace workflows function correctly with the updated version
Caveat AutoTrace is a mature tool with stable command-line interface; minor version upgrades typically have no breaking changes for existing workflows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Autotrace Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9152 — 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-9152 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