Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/image/tiff: excessive CPU consumption from no-op loop iterations [CVE-2023-29407] #61581

Closed
neild opened this issue Jul 25, 2023 · 1 comment
Assignees
Labels
NeedsFix The path to resolution is known, but the work has not been done. Security
Milestone

Comments

@neild
Copy link
Contributor

neild commented Jul 25, 2023

Decoding a 0-height tiled TIFF image iterates over every horizontal pixel. A maliciously-crafted 0-height, max-width image can force 2^32 loop iterations and a substantial amount of CPU consumption.

Thanks to Philippe Antoine (Catena cyber) for reporting this issue.

This is CVE-2023-29407.


This is a PRIVATE issue for CVE-2023-29407, tracked in http://b/279483698 and fixed by http://tg/1944079.

/cc @golang/security and @golang/release

@neild neild added Security NeedsFix The path to resolution is known, but the work has not been done. labels Jul 25, 2023
@gopherbot
Copy link

Change https://go.dev/cl/514897 mentions this issue: tiff: limit work when decoding malicious images

@neild neild changed the title security: fix CVE-2023-29407 image/tiff: excessive CPU consumption from 2^32 no-op loop iterations Aug 1, 2023
@neild neild changed the title image/tiff: excessive CPU consumption from 2^32 no-op loop iterations image/tiff: excessive CPU consumption from no-op loop iterations [CVE-2023-29407] Aug 1, 2023
@neild neild self-assigned this Aug 1, 2023
@dmitshur dmitshur changed the title image/tiff: excessive CPU consumption from no-op loop iterations [CVE-2023-29407] x/image/tiff: excessive CPU consumption from no-op loop iterations [CVE-2023-29407] Aug 2, 2023
@dmitshur dmitshur added this to the Unreleased milestone Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsFix The path to resolution is known, but the work has not been done. Security
Projects
None yet
Development

No branches or pull requests

3 participants