Decoder crash via unchecked frame-rate index
Published Sep 2, 2022 · Updated Aug 3, 2024
Global buffer over-read in PKUVCL davs2 1.6.205 allows local users to crash the decoder by processing a crafted AVS2 bitstream. parse_sequence_header subtracts one from an unvalidated frame_rate_id and uses the result to index the eight-entry FRAME_RATE table, reading four bytes beyond it. Exploitation requires the decoder to process attacker-controlled media; the demonstrated consequence is a decoder crash, with no reported data disclosure or modification.
Summary
What happened
Global buffer over-read in PKUVCL davs2 1.6.205 allows local users to crash the decoder by processing a crafted AVS2 bitstream. parse_sequence_header subtracts one from an unvalidated frame_rate_id and uses the result to index the eight-entry FRAME_RATE table, reading four bytes beyond it. Exploitation requires the decoder to process attacker-controlled media; the demonstrated consequence is a decoder crash, with no reported data disclosure or modification.
The record
- CVE
- CVE-2022-36647
- Published
- Sep 2, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2022CVE 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?
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
- poc1 AVS2 proof of conceptproof 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