Service crash via unchecked GXF track identifier
Published Mar 18, 2021 · Updated Aug 4, 2024
Heap buffer overflow in MediaArea MediaInfo before 20.08 allows remote attackers to crash the application with a crafted GXF file. File_Gxf::ChooseParser_ChannelGrouping subtracts one from an unchecked TrackID and reads Streams[TrackID-1] before the vector boundary. The crash occurs when MediaInfo or a service embedding MediaInfoLib parses attacker-supplied GXF content; no authentication or user interaction is required.
Summary
What happened
Heap buffer overflow in MediaArea MediaInfo before 20.08 allows remote attackers to crash the application with a crafted GXF file. File_Gxf::ChooseParser_ChannelGrouping subtracts one from an unchecked TrackID and reads Streams[TrackID-1] before the vector boundary. The crash occurs when MediaInfo or a service embedding MediaInfoLib parses attacker-supplied GXF content; no authentication or user interaction is required.
The record
- CVE
- CVE-2020-26797
- Published
- Mar 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- GXF crash proof-of-concept fileproof of concept · demonstrated
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