Code execution via incorrect allocated-memory tracking
Published Feb 18, 2025 · Updated Feb 19, 2025
Memory-management flaw in libx264 git master allows attackers to execute arbitrary code by supplying a crafted AAC file. The public CVE record does not identify the affected function or explain how allocated memory is tracked or released incorrectly. Exploitation requires libx264 to process attacker-controlled AAC input; the record reports code execution but does not establish network exposure.
Summary
What happened
Memory-management flaw in libx264 git master allows attackers to execute arbitrary code by supplying a crafted AAC file. The public CVE record does not identify the affected function or explain how allocated memory is tracked or released incorrectly. Exploitation requires libx264 to process attacker-controlled AAC input; the record reports code execution but does not establish network exposure.
The record
- CVE
- CVE-2025-25467
- Published
- Feb 18, 2025
- Updated
- Feb 19, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2025CVE publishedPublication date reported by the CVE source.
- Feb 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo