Skip to content
Fencer Intel
high 8.8

CVE-2022-34300 json

In tinyexr 1.0.1, there is a heap-based buffer over-read in tinyexr::DecodePixelData.

published 4y ago modified 4mo ago also EUVD-2022-37257

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

In tinyexr 1.0.1, there is a heap-based buffer over-read in tinyexr::DecodePixelData.

Patch / fix

  • tinyexr Debian 14, Debian 13, Debian 12 1.0.1+dfsg-4

debian advisories DEBIAN-CVE-2022-34300

  • mame Ubuntu 25.10 0.277+dfsg.1-4ubuntu0.1
  • mame Ubuntu Pro 18.04 LTS 0.195+dfsg.1-2ubuntu0.1~esm1
  • mame Ubuntu Pro 20.04 LTS 0.220+dfsg.1-1ubuntu0.1~esm1
  • mame Ubuntu Pro 22.04 LTS 0.242+dfsg.1-1ubuntu0.1~esm1
  • mame Ubuntu Pro 24.04 LTS 0.264+dfsg.1-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2022-34300

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-34300 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-34300 updated cvss 8.8

tinyexr: heap-based buffer over-read in tinyexr::DecodePixelData

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.49% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/syoyo/tinyexr/issues/167 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.