Local memory corruption via Add Record overflow
Published Feb 11, 2025 · Updated Feb 11, 2025
Stack-based buffer overflow in Code Projects Police FIR Record Management System 1.0 allows local users to corrupt process memory. The Add Record Handler writes record input beyond a stack buffer, but the public record does not identify the affected field or function. A low-privilege local session and no user interaction are required, and a public proof of concept demonstrates the overflow.
Summary
What happened
Stack-based buffer overflow in Code Projects Police FIR Record Management System 1.0 allows local users to corrupt process memory. The Add Record Handler writes record input beyond a stack buffer, but the public record does not identify the affected field or function. A low-privilege local session and no user interaction are required, and a public proof of concept demonstrates the overflow.
The record
- CVE
- CVE-2025-1164
- Published
- Feb 11, 2025
- Updated
- Feb 11, 2025
- Vendor
- Code Projects
- Product
- Police FIR Record Management System
- Classifications
- CWE-787, CWE-121, CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 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?
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
- binary2.pdf 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