Local memory corruption via crafted login username
Published Feb 10, 2025 · Updated Feb 11, 2025
Stack-based buffer overflow in Code Projects Vehicle Parking Management System 1.0 allows local users to corrupt process memory via a username. Public records identify the login function's username argument as the trigger but do not disclose the unsafe C operation or destination stack buffer. A low-privilege local session is required, and published evidence does not establish arbitrary code execution beyond corruption of the application's stack.
Summary
What happened
Stack-based buffer overflow in Code Projects Vehicle Parking Management System 1.0 allows local users to corrupt process memory via a username. Public records identify the login function's username argument as the trigger but do not disclose the unsafe C operation or destination stack buffer. A low-privilege local session is required, and published evidence does not establish arbitrary code execution beyond corruption of the application's stack.
The record
- CVE
- CVE-2025-1163
- Published
- Feb 10, 2025
- Updated
- Feb 11, 2025
- Vendor
- Code Projects
- Product
- Vehicle Parking Management System
- Classifications
- CWE-119, CWE-121, CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 10, 2025CVE publishedPublication date reported by the CVE source.
- Feb 11, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
What conditions does exploitation require?
What is affected?
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
- binary1.pdf proof of conceptproof 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