# CVE-2024-56431: Other in n/a

> An invalid negative left shift in libtheora is disputed as having no security impact, but patches are available for affected distributions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Dec 2024
- **Updated:** 7 May 2025
- **Also known as:** DEBIAN-CVE-2024-56431, GHSA-8xp8-gmmj-xc8w, OESA-2025-1369, SUSE-SU-2025:1287-1, SUSE-SU-2025:1288-1, SUSE-SU-2025:1340-1, SUSE-SU-2025:1365-1, openSUSE-SU-2025:0147-1, openSUSE-SU-2025:15002-1, openSUSE-SU-2025:15009-1

## What is CVE-2024-56431?

CVE-2024-56431 is a critical vulnerability in n/a, published on 25 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

oc_huff_tree_unpack in huffdec.c in libtheora in Theora through 1.0 7180717 has an invalid negative left shift. NOTE: this is disputed by third parties because there is no evidence of a security impact, e.g., an application would not crash.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-56431?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mozjs60` | SUSE:Linux Enterprise Micro 5.1 | All versions | 60.9.0-150200.6.3.1 |
| `mozjs60` | SUSE:Linux Enterprise Micro 5.2 | All versions | 60.9.0-150200.6.3.1 |
| `mozjs60` | SUSE:Linux Enterprise Micro 5.3 | All versions | 60.9.0-150200.6.3.1 |
| `mozjs60` | SUSE:Linux Enterprise Micro 5.4 | All versions | 60.9.0-150200.6.3.1 |
| `mozjs60` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 60.9.0-150200.6.3.1 |
| `mozjs115` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | All versions | 115.4.0-150600.3.9.1 |
| `mozjs60` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | All versions | 60.9.0-150200.6.3.1 |
| `mozjs52` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 52.6.0-150000.3.6.1 |
| `mozjs78` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 78.15.0-150400.3.14.1 |
| `mozjs102` | SUSE:Package Hub 15 SP6 | All versions | 102.15.1-bp156.3.3.1 |
| `mozjs102` | openSUSE:Leap 15.6 | All versions | 102.15.1-bp156.3.3.1 |
| `mozjs115` | openSUSE:Leap 15.6 | All versions | 115.4.0-150600.3.9.1 |
| `mozjs52` | openSUSE:Leap 15.6 | All versions | 52.6.0-150000.3.6.1 |
| `mozjs60` | openSUSE:Leap 15.6 | All versions | 60.9.0-150200.6.3.1 |
| `mozjs78` | openSUSE:Leap 15.6 | All versions | 78.15.0-150400.3.14.1 |
| `mozjs115` | openSUSE:Tumbleweed | All versions | 115.15.0-5.1 |
| `mozjs128` | openSUSE:Tumbleweed | All versions | 128.9.0-2.1 |

Products: Xiph Theora.

## How do I fix CVE-2024-56431?

Apply the vendor's patch.

## Is CVE-2024-56431 being exploited?

There is no known exploitation of CVE-2024-56431 in the wild and no public exploit code.

Public exploit code:

- https://github.com/UnionTech-Software/libtheora-CVE-2024-56431-PoC (github_poc): https://github.com/UnionTech-Software/libtheora-CVE-2024-56431-PoC

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56431 and fix it if it is affected.

What it is: CVE-2024-56431 is a critical vulnerability in n/a, published on 25 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-56431 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-56431/ (Markdown: https://insights.sbomify.com/CVE-2024-56431/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-56431
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-56431
- OSV: https://osv.dev/vulnerability/CVE-2024-56431

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-56431/
Summaries are generated and may contain mistakes; the official description above is the record.