dbcve.org
TinyexrApplication · Tinyexr Project

CVE-2018-12503

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-16
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
tinyexr 0.9.5 has a heap-based buffer over-read in LoadEXRImageFromMemory 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 · moderate confidence

tinyexr 0.9.5 contains a heap-based buffer over-read vulnerability in the LoadEXRImageFromMemory function when parsing EXR image data from memory. This memory safety flaw could allow attackers to read beyond allocated heap buffers, potentially leading to information disclosure, denial of service, or possibly arbitrary code execution depending on memory layout and usage.

MitigationUpdate to a newer version of tinyexr if available, or apply vendor patches. As a workaround, validate EXR input data before passing to LoadEXRImageFromMemory and ensure proper bounds checking is in place.

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
TinyexrApplication
Affected:= 0.9.5

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. Identify tinyexr library version
    Check the installed tinyexr version by examining the library file, headers, or version metadata linked in your application. Common methods: check the library filename (e.g., libtinyexr.a, libtinyexr.so), inspect version.h or tinyexr.h for version defines, or query the compiled library with tools like strings or nm.
    Affected if The installed version is exactly 0.9.5
  2. Confirm application links to tinyexr
    Identify whether your application or any dependent library links against tinyexr by checking build artifacts, dependency lists (ldd on Linux, dumpbin on Windows), or build configuration files.
    Affected if Your code or dependencies link to tinyexr version 0.9.5
  3. Locate usage of LoadEXRImageFromMemory
    Search your codebase for calls to the LoadEXRImageFromMemory function. Use grep, IDE search, or code analysis tools to find invocations of this specific function.
    Affected if Code calls LoadEXRImageFromMemory to parse EXR data from memory buffers
  4. Verify EXR input comes from memory sources
    Examine the data source passed to LoadEXRImageFromMemory calls. Determine if the EXR image data originates from memory buffers, file reads, network streams, or other in-memory sources.
    Affected if EXR image data is loaded from memory buffers rather than only from disk files

You are affected if your environment uses tinyexr version 0.9.5 and your code calls LoadEXRImageFromMemory to parse EXR image data from memory.

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 newer version of tinyexr if available, or apply vendor patches. As a workaround, validate EXR input data before passing to LoadEXRImageFromMemory and ensure proper bounds checking is in place.

Recommended fix Moderate confidence

1.0.x or later stable release

  1. 1. Identify all codebases using tinyexr version 0.9.5 by searching for the header file or library dependency
  2. 2. Locate the project's dependency management file (e.g., package.json, conanfile.txt, CMakeLists.txt, or vendor includes) that specifies tinyexr
  3. 3. Update the version specification from 0.9.5 to the latest stable release (1.0.x or later)
  4. 4. Rebuild and test the application to ensure the library functions correctly with the new version
  5. 5. Verify the fix resolves the heap-based buffer over-read by testing EXR image loading from memory with various input files
Caveat Review release notes between 0.9.5 and target version for any API changes; minor version upgrades typically maintain backward compatibility but verify image loading APIs

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

Fix this in Tinyexr Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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