FFmpeg up to 7.1 AAC Encoder libavcodec/aacenc_tns.c ff_aac_search_for_tns stack-based overflow

Summaryinfo

A vulnerability classified as critical has been found in FFmpeg up to 7.1. The impacted element is the function ff_aac_search_for_tns of the file libavcodec/aacenc_tns.c of the component AAC Encoder. Performing a manipulation results in stack-based overflow. This vulnerability is cataloged as CVE-2025-1594. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in FFmpeg up to 7.1. This affects the function ff_aac_search_for_tns of the file libavcodec/aacenc_tns.c of the component AAC Encoder. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability.

The advisory is shared at trac.ffmpeg.org. This vulnerability is uniquely identified as CVE-2025-1594. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details and a public exploit are known.

The exploit is shared for download at trac.ffmpeg.org. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 265685 (Debian dsa-6007 : ffmpeg - security update), 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 databases at Tenable (265685) and CERT Bund (WID-SEC-2025-0429). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Ubuntu Linux
  • Open Source ffmpeg

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍

CVSSv3info

VulDB Meta Base Score: 7.1
VulDB Meta Temp Score: 7.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CNA Base Score: 6.3
CNA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Stack-based overflow
CWE: CWE-121 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 265685
Nessus Name: Debian dsa-6007 : ffmpeg - security update

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/22/2025 🔍
02/22/2025 +0 days 🔍
09/22/2025 +212 days 🔍

Sourcesinfo

Product: ffmpeg.org

Advisory: trac.ffmpeg.org
Status: Confirmed

CVE: CVE-2025-1594 (🔍)
GCVE (CVE): GCVE-0-2025-1594
GCVE (VulDB): GCVE-100-296589
CERT Bund: WID-SEC-2025-0429 - ffmpeg: Schwachstelle ermöglicht Denial of Service, potentiell Codeausführung

scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 02/22/2025 23:15
Updated: 09/22/2025 13:40
Changes: 02/22/2025 23:15 (57), 02/23/2025 22:32 (30), 06/04/2025 07:17 (12), 09/06/2025 13:21 (7), 09/22/2025 13:40 (2)
Complete: 🔍
Submitter: 0x20z
Cache ID: 216::103

Submitinfo

Accepted

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!