Local crash via unsafe myStrCpy copy
Published Feb 5, 2022 · Updated Aug 4, 2024
Buffer overflow in perM 0.4.0 allows local users to crash the read mapper by processing crafted sequence input. The myStrCpy wrapper passes a caller-supplied size minus one to strncpy, which pads the destination through that bound instead of limiting the copy to its actual capacity. The vulnerable path is reached when the command-line mapper reads supplied FASTA data; the demonstrated consequence is process termination, not confirmed code execution.
Summary
What happened
Buffer overflow in perM 0.4.0 allows local users to crash the read mapper by processing crafted sequence input. The myStrCpy wrapper passes a caller-supplied size minus one to strncpy, which pads the destination through that bound instead of limiting the copy to its actual capacity. The vulnerable path is reached when the command-line mapper reads supplied FASTA data; the demonstrated consequence is process termination, not confirmed code execution.
The record
- CVE
- CVE-2021-38172
- Published
- Feb 5, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 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.
Weakness, pattern, technique
Public exploit references
- Debian perM buffer-overflow regression testproof 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