CVE-2018-12064
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 · uneditedtinyexr 0.9.5 has a heap-based buffer over-read via tinyexr::ReadChannelInfo in tinyexr.h.
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 confidencetinyexr 0.9.5 contains a heap-based buffer over-read vulnerability in the ReadChannelInfo function in tinyexr.h. An attacker can exploit this by providing a specially crafted EXR file that causes the function to read beyond allocated heap memory boundaries, potentially leading to information disclosure or denial of service.
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.9.5CVSS 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.
-
Locate tinyexr library in the environmentSearch for files named tinyexr.h, libtinyexr.so, libtinyexr.a, or tinyexr.lib in common system library and include directories. On Linux: find /usr -name "*tinyexr*" 2>/dev/null. On Windows: search in development folders and installed package directories.Affected if tinyexr library files are found in the system
-
Determine the installed tinyexr versionOpen the tinyexr.h header file and look for version defines near the top of the file (often #define TINYEXR_VERSION or similar). If using a compiled library, check any associated version metadata or the package that installed it.Affected if The version is exactly 0.9.5
-
Identify applications using tinyexr to parse EXR filesSearch project source code or installed binaries for includes of tinyexr.h and calls to LoadEXR, ExrLoad, or related EXR loading functions. Check application dependencies for linkage to libtinyexr.Affected if Applications link against tinyexr and process EXR image files
-
Verify if untrusted EXR files are processedReview the application's file handling behavior to determine if it accepts EXR input from untrusted sources (user uploads, network input, or external files without validation).Affected if The application processes EXR files from untrusted or external sources using the vulnerable tinyexr library
The environment is affected if tinyexr version 0.9.5 is installed AND an application uses it to parse EXR files, particularly from untrusted sources, enabling the heap buffer over-read when a specially crafted EXR is processed.
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 dataUpdate tinyexr to the latest version that includes bounds checking fixes in the ReadChannelInfo function, or apply a patch that adds proper validation of channel data sizes before reading from the heap buffer.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12064 — 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-12064 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