CVE-2017-18198
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 · uneditedprint_iso9660_recurse in iso-info.c in GNU libcdio before 1.0.0 allows remote attackers to cause a denial of service (heap-based buffer over-read) or possibly have unspecified other impact via a crafted iso file.
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 over-read vulnerability exists in the print_iso9660_recurse function in iso-info.c of GNU libcdio versions prior to 1.0.0. The vulnerability occurs during ISO 9660 file parsing when the code reads beyond allocated heap buffer boundaries, potentially allowing remote attackers to cause a denial of service or achieve unspecified impact via a specially crafted ISO file.
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.0.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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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.
-
Verify if GNU libcdio is installedUse your system's package manager or check for libcdio library files (e.g., libcdio.so on Linux, libcdio.dylib on macOS) in standard library directoriesAffected if libcdio is installed and its version is less than 1.0.0
-
Determine the installed libcdio versionRun 'pkg-config --modversion libcdio' or check via your package manager (e.g., 'dpkg -l libcdio', 'rpm -q libcdio', or 'brew list libcdio')Affected if The returned version is below 1.0.0
-
Confirm the iso-info tool is presentLocate the iso-info binary in your system (commonly in /usr/bin, /usr/local/bin, or via 'which iso-info')Affected if iso-info executable exists on the system
-
Check the version of the iso-info toolRun 'iso-info --version' or 'iso-info -V'Affected if The reported version is prior to 1.0.0, indicating it was built against a vulnerable libcdio library
-
Identify if untrusted ISO files are being processedReview system logs, cron jobs, or application configurations for automated processing of ISO files from untrusted sources, or inspect any scripts that invoke iso-info or libcdio-based toolsAffected if The system processes ISO files from untrusted or external sources using libcdio tools
A system is affected if it runs any version of GNU libcdio or iso-info prior to 1.0.0 and processes potentially untrusted ISO 9660 files with those tools.
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 data1.0.0
Update GNU libcdio to version 1.0.0 or later which contains the bounds-checking fix. Until the update is applied, avoid processing untrusted ISO files with iso-info or related libcdio tools.
- Consultation2.0 h
- Implementation3.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18198 — 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-18198 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