Heap overwrite via SOFA header parsing
Published Oct 29, 2021 · Updated Aug 3, 2024
Heap-based buffer overflow in libmysofa before 1.2.1 allows attackers to crash consuming applications via crafted SOFA files. The loudness(), mysofa_check(), and readOHDRHeaderMessageDataLayout() paths process attacker-controlled SOFA header sizes without sufficient heap bounds, allowing writes beyond allocated buffers. An attacker must supply a malicious SOFA file to an application that invokes these library routines; the consequence is process interruption and possible memory corruption.
Summary
What happened
Heap-based buffer overflow in libmysofa before 1.2.1 allows attackers to crash consuming applications via crafted SOFA files. The loudness(), mysofa_check(), and readOHDRHeaderMessageDataLayout() paths process attacker-controlled SOFA header sizes without sufficient heap bounds, allowing writes beyond allocated buffers. An attacker must supply a malicious SOFA file to an application that invokes these library routines; the consequence is process interruption and possible memory corruption.
The record
- CVE
- CVE-2021-3756
- Published
- Oct 29, 2021
- Updated
- Aug 3, 2024
- Vendor
- Symonics GmbH
- Product
- libmysofa
- Classifications
- CWE-122, CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <1.2.1
What conditions does exploitation require?
What is affected?
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.
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