Global-buffer-overflow in libxaac: iusace_quantize_lines

libxaac Updated 02 Oct 2025

Summary

14/10/2023
N/A
Yes i
Unrated
Not published

OSV-2023-1012: Global-buffer-overflow in iusace_quantize_lines. Affects libxaac versions >= 1a62ab2e920382e878f6d11a26c0bcefbb7710f7, < e8d026548e88221580cbaeb7a8906bced0295402. Fixed in e8d026548e88221580cbaeb7a8906bced0295402. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

libxaac is an open-source library that provides encoding and decoding functionality for Advanced Audio Coding (AAC) audio files. It is widely used in various applications and platforms for audio processing. However, a vulnerability has been discovered in the library, specifically in the function iusace_quantize_lines, which can lead to a global buffer overflow.

Vulnerability Detail

The vulnerability in libxaac arises due to a global buffer overflow in the iusace_quantize_lines function. This can be triggered when processing certain input data, causing a read of 4 bytes beyond the bounds of the buffer. An attacker could potentially exploit this vulnerability to execute arbitrary code, crash the application, or disclose sensitive information.

How To Fix

Minimum fixed version

e8d026548e88221580cbaeb7a8906bced0295402

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, developers can implement input validation and boundary checks in their applications to prevent triggering the buffer overflow. Here is an example of how to perform input validation in C:

void process_input_data(const char* data, size_t length) {
  if (length > MAX_BUFFER_SIZE) {
    // Handle error or reject input
    return;
  }

  // Process the input data
}

Conclusion

In conclusion, libxaac is vulnerable to a global buffer overflow in the iusace_quantize_lines function. This can be exploited by an attacker to execute arbitrary code, crash the application, or disclose sensitive information. It is crucial for developers to update their dependencies and rebuild affected applications with the fixed version of libxaac. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libxaac →

Share this vulnerability

FAQ

libxaac is an open-source library that provides encoding and decoding functionality for Advanced Audio Coding (AAC) audio files. It is widely used in various applications and platforms for audio processing.

A global buffer overflow occurs when a program writes data beyond the bounds of a buffer, potentially overwriting adjacent memory. This can lead to crashes, code execution, or disclosure of sensitive information.

An attacker can exploit this vulnerability by providing specially crafted input data that triggers the buffer overflow. This can allow them to execute arbitrary code, crash the application, or potentially access sensitive information.

Yes, the vulnerability has been fixed in the libxaac library. Developers should update to a version that includes the fix to ensure their applications are not vulnerable.

As a temporary workaround, developers can implement input validation and boundary checks in their applications to prevent triggering the buffer overflow. However, updating to a fixed version of libxaac is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for libxaac.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

e8d026548e88221580cbaeb7a8906bced0295402

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback