CVE-2022-41793

What it actually does

Out-of-bounds write in CSR format title parsing allows memory corruption that can be leveraged for arbitrary code execution when a malformed file is processed.

Why it matters to the business

Processing untrusted chemical structure files on affected systems can lead to full host compromise, data theft, or ransomware deployment with moderate urgency given low EPSS and no known active campaigns.

How an attack unfolds

An attacker crafts a malformed CSR file containing an oversized or invalid title field, delivers it to a victim who opens it with Open Babel or a dependent tool, triggering the out-of-bounds write that corrupts memory and allows shellcode execution.

How to fix it

Upgrade Open Babel to a version containing the fix for the CSR title parsing logic; if no fixed release is yet available, replace the library with a patched build or isolate file processing in a sandbox until an update is released.

How to confirm the fix worked

Confirm the installed Open Babel version is newer than 3.1.1 and master commit 530dbfa3; test by attempting to parse known-good and known-malformed CSR samples in a controlled environment and verify no crash or unexpected memory writes occur.

Typical attack path

1. Create or obtain a specially crafted CSR file with malicious title data
2. Deliver the file via email, download link, or shared storage
3. Victim opens the file using Open Babel CLI, GUI, or an application that embeds the library
4. Out-of-bounds write occurs during title parsing
5. Attacker-supplied payload executes with the privileges of the Open Babel process

How to detect it

Review process creation logs and file-access telemetry for invocations of obabel or babel with CSR files; monitor for unexpected crashes or memory-corruption signals in chemistry-processing applications.

What your security team should do

• Inventory all systems and pipelines that invoke Open Babel or link against libopenbabel
• Apply available updates or rebuild from patched source as soon as a fixed version is published
• Restrict Open Babel execution to non-privileged accounts and sandboxed environments
• Add file-type filtering or content scanning before chemical file processing workflows