Memory corruption via unbounded username input
Published Oct 25, 2024 · Updated Oct 25, 2024
Buffer overflow in SourceCodester Payroll Management System 1.0 allows local users to corrupt memory through an oversized username. The login() function reads UserName with an unbounded cin extraction into a 30-byte array, overwriting adjacent memory after 30 characters. Exploitation requires interactive access to the running program, and the published steps establish memory corruption rather than achieved code execution.
Summary
What happened
Buffer overflow in SourceCodester Payroll Management System 1.0 allows local users to corrupt memory through an oversized username. The login() function reads UserName with an unbounded cin extraction into a 30-byte array, overwriting adjacent memory after 30 characters. Exploitation requires interactive access to the running program, and the published steps establish memory corruption rather than achieved code execution.
The record
- CVE
- CVE-2024-10371
- Published
- Oct 25, 2024
- Updated
- Oct 25, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 25, 2024CVE publishedPublication date reported by the CVE source.
- Oct 25, 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
- Payroll Management System in C++ with Source Code v1.0 - Buffer Overflowproof of concept · unverified
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