Memory corruption via realloc-failure double free
Published Oct 17, 2022 · Updated Jan 24, 2026
Double free in the shpsrt utility in OSGeo Shapelib 1.5.0 and earlier allows attackers to corrupt process memory. The split() error path frees the copy buffer after realloc() fails and then releases the same buffer again during cleanup. Reaching the flaw requires an allocation failure while shpsrt parses sort criteria; the resulting heap corruption can crash the process or enable code execution.
Summary
What happened
Double free in the shpsrt utility in OSGeo Shapelib 1.5.0 and earlier allows attackers to corrupt process memory. The split() error path frees the copy buffer after realloc() fails and then releases the same buffer again during cleanup. Reaching the flaw requires an allocation failure while shpsrt parses sort criteria; the resulting heap corruption can crash the process or enable code execution.
The record
- CVE
- CVE-2022-0699
- Published
- Oct 17, 2022
- Updated
- Jan 24, 2026
- Vendor
- Open Source Geospatial Foundation (OSGeo)
- Product
- Shapelib
- Classifications
- CWE-416, CWE-415
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 17, 2022CVE publishedPublication date reported by the CVE source.
- Jan 24, 2026Record 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=shapelib 1.5.0 and older releases
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
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