Memory corruption via unbounded Ethernet interface name
Published Aug 11, 2025 · Updated Aug 11, 2025
Heap-based buffer overflow in libcsp 2.0 allows attackers to corrupt process memory through an oversized Ethernet interface name. The csp_eth_init function passes the unbounded ifname string to strcpy for ctx->name, writing beyond the heap allocation above CSP_IFLIST_NAME_MAX. Reachability requires control of the interface name supplied by the caller; an out-of-bounds heap write is demonstrated, but code execution is not established.
Summary
What happened
Heap-based buffer overflow in libcsp 2.0 allows attackers to corrupt process memory through an oversized Ethernet interface name. The csp_eth_init function passes the unbounded ifname string to strcpy for ctx->name, writing beyond the heap allocation above CSP_IFLIST_NAME_MAX. Reachability requires control of the interface name supplied by the caller; an out-of-bounds heap write is demonstrated, but code execution is not established.
The record
- CVE
- CVE-2025-51823
- Published
- Aug 11, 2025
- Updated
- Aug 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
No public exploit references are available in this record.
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