CVE-2022-42885
High · 7.8CVSS
7.8
EPSS
0.8%
Published
Jul 21, 2023
CISA due date
—
Cloudanix analysis
A bug in a popular chemistry software tool can let attackers take over a computer if someone opens a specially made data file.
- Exploitation
- Requires User Interaction
- Attacker needs
- User Interaction
- Complexity
- Low
- Impact
- Full Compromise
- Component
- Library
- Class
- Memory Corruption
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Use of an uninitialized pointer in the GRO format reader allows a malformed input file to trigger memory corruption leading to arbitrary code execution in the context of the parsing process.
Why it matters to the business
Organizations that process chemistry or molecular files with Open Babel face risk of full system compromise when users open attacker-supplied files, potentially enabling malware deployment or data theft.
How an attack unfolds
An attacker crafts a specially malformed GRO file that leaves a pointer uninitialized during resource parsing. The victim opens the file using Open Babel 3.1.1 or the vulnerable master branch; the uninitialized pointer is dereferenced, corrupting memory and allowing the attacker to hijack control flow for code execution.
How to fix it
Upgrade to a patched version of Open Babel once released by the project maintainers; in the interim, avoid opening untrusted GRO or other molecular files with Open Babel 3.1.1 or commit 530dbfa3.
How to confirm the fix worked
Confirm Open Babel version is newer than 3.1.1 and does not contain commit 530dbfa3; test by attempting to parse known-malformed sample files in a controlled environment and verify no crash or unexpected code paths execute.
Typical attack path
- Craft malicious GRO file exploiting uninitialized pointer in res parsing
- Deliver file via email, download link, or shared storage
- Victim opens file with vulnerable Open Babel binary
- Memory corruption occurs and attacker payload executes
How to detect it
Review file-access and process-creation logs for invocations of Open Babel against GRO files from untrusted sources; look for unexpected crashes or child processes spawned immediately after file parsing.
What your security team should do
- Block or sandbox Open Babel usage with untrusted files until a fix is available
- Monitor upstream Open Babel repository for security patches and apply immediately
- Educate users handling molecular data files about the risk of opening unsolicited files
The record
A use of uninitialized pointer vulnerability exists in the GRO format res functionality of Open Babel 3.1.1 and master commit 530dbfa3. A specially crafted malformed file can lead to arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Debian:11 | openbabel | 0 | No fix |
| Debian:12 | openbabel | 0 | No fix |
| Debian:13 | openbabel | 0 | No fix |
| Debian:14 | openbabel | 0 | No fix |
| Ubuntu:16.04:LTS | openbabel | 0 | No fix |
| Ubuntu:18.04:LTS | openbabel | 0 | No fix |
| Ubuntu:20.04:LTS | openbabel | 0 | No fix |
| Ubuntu:22.04:LTS | openbabel | 0 | No fix |
| Ubuntu:24.04:LTS | openbabel | 0 | No fix |
| Ubuntu:24.10 | openbabel | 0 | No fix |
| Ubuntu:25.04 | openbabel | 0 | No fix |
| Ubuntu:25.10 | openbabel | 0 | No fix |
| Ubuntu:Pro:16.04:LTS | openbabel | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | openbabel | 0 | No fix |
| Ubuntu:Pro:20.04:LTS | openbabel | 0 | No fix |
| openSUSE:Leap 16.0 | openbabel | 0 | 3.2.0-bp160.1.1 |
Related vulnerabilities
- CVE-2022-46294 Multiple out-of-bounds write vulnerabilities exist in the translationVectors parsing… Also affects openbabel
- CVE-2022-46293 Multiple out-of-bounds write vulnerabilities exist in the translationVectors parsing… Also affects openbabel
- CVE-2022-46295 Multiple out-of-bounds write vulnerabilities exist in the translationVectors parsing… Also affects openbabel
- CVE-2022-37331 An out-of-bounds write vulnerability exists in the Gaussian format orientation… Also affects openbabel
- CVE-2022-43607 An out-of-bounds write vulnerability exists in the MOL2 format attribute and value… Also affects openbabel
- CVE-2022-41793 An out-of-bounds write vulnerability exists in the CSR format title functionality of Open… Also affects openbabel
- CVE-2022-43467 An out-of-bounds write vulnerability exists in the PQS format coord_file functionality of… Also affects openbabel
- CVE-2022-46290 Multiple out-of-bounds write vulnerabilities exist in the ORCA format nAtoms… Also affects openbabel