CVE-2022-43607

What it actually does

Out-of-bounds write during MOL2 format attribute and value parsing that permits arbitrary code execution when a malformed file is processed.

Why it matters to the business

Processing untrusted molecular data files on systems running Open Babel can lead to full host compromise, disrupting research workflows and potentially exposing sensitive chemical or proprietary data.

How an attack unfolds

An attacker creates a specially malformed MOL2 file containing crafted attribute and value entries that trigger an out-of-bounds write; the file is delivered to a victim who opens it locally with Open Babel, resulting in arbitrary code execution on the victim's system.

How to fix it

No fixed versions are currently listed; discontinue use of Open Babel for untrusted MOL2 files, apply sandboxing or container isolation around the parser, and monitor the project for security updates or patches.

How to confirm the fix worked

Confirm that Open Babel is not invoked on untrusted input by reviewing application dependencies and file-handling workflows; re-test with known proof-of-concept files after any upstream updates become available.

Typical attack path

1. Craft a malicious MOL2 file with malformed attribute/value data
2. Deliver the file to the target via email, download, or shared storage
3. Victim opens the file using Open Babel or an application that invokes its MOL2 parser
4. Out-of-bounds write occurs and attacker-controlled code executes

How to detect it

Review system and application logs for Open Babel crashes or unexpected terminations while processing MOL2 files; inspect process creation events following MOL2 file access for anomalous child processes.

What your security team should do

• Block or quarantine MOL2 files from untrusted sources until a patch is released
• Isolate Open Babel usage inside sandboxed or containerized environments
• Replace Open Babel with alternative chemistry libraries where feasible
• Monitor upstream project announcements for security fixes