Security readout for executives and security teams
Plain-English summary
Open Babel has a memory corruption flaw when handling malformed MOL2 files. If an exposed service processes attacker-supplied molecular files with the affected version, the issue could allow code execution. The bundle does not show known active exploitation.
Executive priority
Treat as high priority where Open Babel processes files from outside trusted teams. The business risk is remote compromise of systems handling scientific file conversion, but urgency depends on actual MOL2 exposure.
Technical view
CVE-2022-43607 is an out-of-bounds write in Open Babel 3.1.1 and master commit 530dbfa3 within MOL2 attribute and value parsing. Talos and CVE describe arbitrary code execution from a crafted malformed file. CVSS 3.1 is 8.1, with high confidentiality, integrity, and availability impact.
Likely exposure
Systems are likely exposed if they run affected Open Babel builds and accept or process untrusted MOL2 files, especially upload, conversion, scientific workflow, or API processing paths.
Exploitation context
The source bundle says an attacker can provide a malicious file to trigger the bug. KEV is false, and no cited source states active exploitation.
Researcher notes
Evidence is limited to CVE and Talos details in the bundle. The affected surface is MOL2 attribute/value parsing. Avoid assuming other Open Babel versions, active exploitation, or a specific fixed version without vendor confirmation.
Mitigation direction
- Inventory Open Babel usage across applications, containers, and scientific processing jobs.
- Check vendor or project guidance for a fixed release or official remediation.
- Restrict untrusted MOL2 ingestion until remediation is confirmed.
- Run Open Babel file processing in isolated, least-privileged environments.
- Add allowlists and size/type controls for molecular file uploads.
Validation and detection
- Confirm whether Open Babel 3.1.1 or commit 530dbfa3 is present.
- Map every public or partner path that accepts MOL2 files.
- Check whether automated workflows process email, upload, or API-submitted MOL2 files.
- Verify parser jobs run with limited privileges and containment.
- Record remediation status against each affected service or image.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-43607 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.