Control-flow corruption via overlong Markdown character run
Published Jul 2, 2022 · Updated Aug 3, 2024
Stack-based buffer overflow in md2roff 1.7 allows attackers to crash the converter by processing a crafted Markdown file. The Markdown parser writes an overlong run of consecutive input characters past a stack buffer, and the published proof of concept overwrites RIP. Exploitation requires processing attacker-controlled input; the vendor disputes the issue because the utility is not intended for untrusted files.
Summary
What happened
Stack-based buffer overflow in md2roff 1.7 allows attackers to crash the converter by processing a crafted Markdown file. The Markdown parser writes an overlong run of consecutive input characters past a stack buffer, and the published proof of concept overwrites RIP. Exploitation requires processing attacker-controlled input; the vendor disputes the issue because the utility is not intended for untrusted files.
The record
- CVE
- CVE-2022-34913
- Published
- Jul 2, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 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.
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
- CVE-2022-34913 AFL++ 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