Local encoder crash via pre-check NULL dereference
Published Mar 10, 2022 · Updated Aug 4, 2024
NULL pointer dereference in rockcarry ffjpeg allows local users to crash the encoder by processing a crafted BMP input file. Crafted input leads jfif_encode to call bitstr_tell with a null stream, and bitstr_tell reads the type field before checking the pointer. Exploitation requires a user to invoke the encoder on the file and interrupts only that process.
Summary
What happened
NULL pointer dereference in rockcarry ffjpeg allows local users to crash the encoder by processing a crafted BMP input file. Crafted input leads jfif_encode to call bitstr_tell with a null stream, and bitstr_tell reads the type field before checking the pointer. Exploitation requires a user to invoke the encoder on the file and interrupts only that process.
The record
- CVE
- CVE-2021-34122
- Published
- Mar 10, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2022CVE 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
- ffjpeg bitstr_tell crash 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