CVE-2024-5171: Integer overflow in libaom internal function img_alloc_helper can lead to heap buffer overflow

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2024-5171 is a critical-severity flaw (CVSS 9.8) affecting libaom. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Integer overflow in libaom internal function img_alloc_helper can lead to heap buffer overflow. This function can be reached via 3 callers: * Calling aom_img_alloc() with a large value of the d_w, d_h, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid. * Calling aom_img_wrap() with a large value of the d_w, d_h, or align para

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.3% (top 30%)
CISA exploited list	No
Weakness	CWE-20, CWE-190
Published	2024-06-05
Last modified	2026-06-17

Publisher (CNA): Google Inc. · Vendor: aomedia

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-06-05 20:15 UTCPublished CVE record published
2026-06-17 08:15 UTCUpdated Record last modified

aomedia libaom UPGRADE

Affected: >= 1.0.0 and <= 3.9.0

Fixed in: newer than 3.9.0

Safe to downgrade to: a release before 1.0.0

1. Check installed version

apt-cache policy libaom || rpm -q libaom || libaom --version

2. UPGRADE to newer than 3.9.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libaom

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libaom

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)

apt-cache madison libaom sudo apt install libaom=<VERSION_BEFORE_1.0.0> sudo apt-mark hold libaom

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list libaom sudo dnf downgrade libaom-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add libaom

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-5171?

libaom: upgrade to newer than 3.9.0. Exact commands for each OS are on this page.

Is CVE-2024-5171 being exploited?

CVE-2024-5171 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-5171 affect?

CVE-2024-5171 affects libaom. Severity is critical (CVSS 9.8). Integer overflow in libaom internal function img_alloc_helper can lead to heap buffer overflow. This function can be reached via 3 callers: * Calling aom_img_alloc() with a large value of the d_w, d_h, or align parameter may result in

How urgent is CVE-2024-5171?

Priority 62/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs