Process memory corruption via unchecked command input
Published Oct 28, 2025 · Updated Oct 28, 2025
Stack-based buffer overflow in Ericsson CodeChecker 6.26.1 and earlier allows local users to corrupt process memory via crafted build input. The ldlogger library copies an attacker-controlled command-line string with strcpy into a fixed 4096-byte stack buffer without checking its length. The flaw is reachable only when CodeChecker log processes untrusted local command input, exposing data and execution integrity within that process.
Summary
What happened
Stack-based buffer overflow in Ericsson CodeChecker 6.26.1 and earlier allows local users to corrupt process memory via crafted build input. The ldlogger library copies an attacker-controlled command-line string with strcpy into a fixed 4096-byte stack buffer without checking its length. The flaw is reachable only when CodeChecker log processes untrusted local command input, exposing data and execution integrity within that process.
The record
- CVE
- CVE-2025-40843
- Published
- Oct 28, 2025
- Updated
- Oct 28, 2025
- Vendor
- Ericsson
- Product
- CodeChecker
- Classifications
- CWE-121, CAPEC-100
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 28, 2025CVE publishedPublication date reported by the CVE source.
- Oct 28, 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=0 <=6.26.1
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.
Public exploit references
- Ericsson command-line overflow 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