Process crash via undisclosed access violation
Published Feb 15, 2023 · Updated Mar 19, 2025
Access violation in Hasherezade LibPeConv before commit b076013 allows remote attackers to crash a consuming process via crafted input. The published CVE record identifies no affected function or invalid memory operation, and the upstream repository does not publicly tie the fixing commit to a code-level cause. Exposure depends on an application passing attacker-controlled PE data to the embedded library; LibPeConv itself provides no network service.
Summary
What happened
Access violation in Hasherezade LibPeConv before commit b076013 allows remote attackers to crash a consuming process via crafted input. The published CVE record identifies no affected function or invalid memory operation, and the upstream repository does not publicly tie the fixing commit to a code-level cause. Exposure depends on an application passing attacker-controlled PE data to the embedded library; LibPeConv itself provides no network service.
The record
- CVE
- CVE-2023-23461
- Published
- Feb 15, 2023
- Updated
- Mar 19, 2025
- Vendor
- Hasherezade
- Product
- LibPeConv
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 15, 2023CVE publishedPublication date reported by the CVE source.
- Mar 19, 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=before commit b076013 (30/11/2022). <Update to the latest version
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
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