stb_vorbis OGG Vorbis File start_decoder out-of-bounds write

Summaryinfo

A vulnerability has been found in stb_vorbis and classified as critical. The impacted element is the function start_decoder of the component OGG Vorbis File Handler. This manipulation causes out-of-bounds write. This vulnerability is registered as CVE-2023-45681. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability has been found in stb_vorbis (the affected version unknown) and classified as critical. Affected by this vulnerability is the function start_decoder of the component OGG Vorbis File Handler. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

stb_vorbis is a single file MIT licensed library for processing ogg vorbis files. A crafted file may trigger memory write past an allocated heap buffer in `start_decoder`. The root cause is a potential integer overflow in `sizeof(char*) * (f->comment_list_length)` which may make `setup_malloc` allocate less memory than required. Since there is another integer overflow an attacker may overflow it too to force `setup_malloc` to return 0 and make the exploit more reliable. This issue may lead to code execution.

The weakness was published 10/21/2023 as GHSL-2023-145. The advisory is shared at securitylab.github.com. This vulnerability is known as CVE-2023-45681 since 10/10/2023. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/13/2025).

The vulnerability scanner Nessus provides a plugin with the ID 213982 (Fedora 40 : libxmp (2025-c58133e520)), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (213982). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• stb_vorbis

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion