Skip to content
Fencer Vulns
medium 6.5

CVE-2023-29407 json

Excessive CPU consumption when decoding 0-height images in golang.org/x/image/tiff

published 2023-08-02 3 y ago modified 2026-06-17 4 mo ago also GHSA-j3p8-6mrq-6g7h , GO-2023-1990 , EUVD-2023-2307

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

Summary

A maliciously-crafted image can cause excessive CPU consumption in decoding. A tiled image with a height of 0 and a very large width can cause excessive CPU consumption, despite the image size (width * height) appearing to be zero.

Patch / fix

  • go golang.org/x/image 0.10.0
  • golang.org/x/image golang.org/x/image/tiff 0.10.0
  • golang-golang-x-image Debian 14, Debian 13 0.11.0-1

debian advisories DEBIAN-CVE-2023-29407

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-2023-29407 updated cvss 6.5

golang.org/x/image/tiff: excessive CPU consumption in decoding

  • Red Hat Advanced Cluster Management for Kubernetes 2 acm-cluster-templates-operator-container
    affected: no fix planned “Will not fix”

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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.87% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go golang.org/x/image
<0.10.0
0.10.0

Affected products

  • golang.org/x/image golang.org/x/image/tiff

Classification

Weakness

References

Sources

Fencer Vulns 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.