Debian LinuxOperating system · Debian
CVE-2018-5818
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 · uneditedAn error within the "parse_rollei()" function (internal/dcraw_common.cpp) within LibRaw versions prior to 0.19.1 can be exploited to trigger an infinite loop.
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 programming error in the parse_rollei() function within LibRaw's dcraw_common.cpp can be exploited to trigger an infinite loop, causing a denial of service. This is triggered when processing specially crafted Rollei raw image 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
Debian LinuxOperating system
= 8.0< 0.19.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 LibRaw is installedOn Debian-based systems: dpkg -l | grep libraw or check for libraw library files in /usr/lib/ or /usr/local/lib/. On other systems, look for libraw shared objects (libraw.so, libraw.a) in standard library paths.Affected if LibRaw library is present on the system
-
Determine installed LibRaw versionRun: dpkg -l libraw (Debian) or check the library version directly: strings /usr/lib/x86_64-linux-gnu/libraw.so | grep -i version or check the package metadata. Also check libraw.h header if available for version macros.Affected if Version is lower than 0.19.1 (e.g., 0.18.x, 0.17.x, etc.)
-
Verify Rollei raw file processing capability existsCheck if the dcraw_common.cpp component is present in the installed LibRaw source or binary package. Look for the parse_rollei function symbol: nm -C /usr/lib/libraw.so | grep -i rolleiAffected if The parse_rollei function symbol is found in the binary, meaning Rollei raw format support is compiled in
-
Check for applications using LibRaw to process imagesIdentify applications linked against libraw that could process user-supplied raw image files: ldd <image_app> | grep libraw or check for packages that depend on libraw (e.g., darktable, rawtherapee, digikam).Affected if Applications capable of loading and processing raw images via LibRaw are installed and can handle Rollei formats
A system is affected if LibRaw version is installed and is lower than 0.19.1, and the parse_rollei function for processing Rollei raw images is available in the binary.
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 data0.19.1
Upgrade LibRaw to version 0.19.1 or later to patch the infinite loop vulnerability in the parse_rollei() function.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5818 — 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-2018-5818 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