Code execution via uninitialized residue pointer
Published Jul 21, 2023 · Updated Aug 3, 2024
Memory corruption in Open Babel 3.1.1 allows attackers to execute code when the converter or API parses a crafted GRO file. GROFormat::ReadMolecule treats an initial residue ID of zero as an existing residue, then calls AddAtom and SetAtomID through an uninitialized res pointer. Exploitation requires the CLI, API, or language bindings to parse the malicious file; Talos demonstrated a crash and found that the stack pointer can enable arbitrary code execution.
Summary
What happened
Memory corruption in Open Babel 3.1.1 allows attackers to execute code when the converter or API parses a crafted GRO file. GROFormat::ReadMolecule treats an initial residue ID of zero as an existing residue, then calls AddAtom and SetAtomID through an uninitialized res pointer. Exploitation requires the CLI, API, or language bindings to parse the malicious file; Talos demonstrated a crash and found that the stack pointer can enable arbitrary code execution.
The record
- CVE
- CVE-2022-42885
- Published
- Jul 21, 2023
- Updated
- Aug 3, 2024
- Vendor
- Open Babel
- Product
- Open Babel
- Classifications
- CWE-824, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2023CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=3.1.1
- Affected versionversion=master commit 530dbfa3
What conditions does exploitation require?
What is affected?
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
- Cisco Talos malformed GRO 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