LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43467: An out-of-bounds write vulnerability exists in the PQS format coord_file functionality of Open Babel 3.1.1...

An out-of-bounds write vulnerability exists in the PQS format coord_file 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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Open Babel can be crashed or potentially taken over when it processes a malicious PQS molecular file. The source states this can lead to arbitrary code execution in Open Babel 3.1.1 and one master commit. Treat systems that automatically process external chemistry files as high priority.

Executive priority

Prioritize remediation for internet-facing, shared, or automated file-processing environments. The business risk is highest where untrusted scientific files are parsed without isolation.

Technical view

The flaw is an out-of-bounds write in Open Babel's PQS format coord_file functionality. A specially crafted malformed file can trigger memory corruption and possible arbitrary code execution. The CVE lists Open Babel 3.1.1 and master commit 530dbfa3 as affected.

Likely exposure

Exposure is most likely where Open Babel processes PQS files from users, partners, email attachments, uploads, pipelines, or public datasets. The bundle does not identify downstream packaged products or hosted services.

Exploitation context

The CVE says an attacker can provide a malicious file to trigger the vulnerability. CISA KEV is not cited, and the provided bundle does not show active exploitation in the wild.

Researcher notes

Evidence is limited to the CVE bundle and Talos advisory reference. The reported impact is arbitrary code execution via malformed PQS parsing, but no exploit-in-the-wild evidence or specific fixed version is included here.

Mitigation direction

  • Inventory Open Babel installations and confirm whether 3.1.1 or commit 530dbfa3 is present.
  • Check Open Babel and Talos guidance for fixed versions or vendor-supported remediation.
  • Temporarily avoid processing untrusted PQS files until remediation is confirmed.
  • Isolate file conversion workflows with least privilege and constrained runtime access.
  • Monitor CVE, Talos, and vendor advisories for updated remediation details.

Validation and detection

  • Search servers, containers, CI images, and workstations for Open Babel binaries and libraries.
  • Confirm whether applications accept or automatically process PQS files.
  • Review upload, batch conversion, and research pipeline paths for untrusted file ingestion.
  • Verify remediated systems no longer report affected Open Babel versions.
  • Document compensating controls where upgrade status is pending.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
description · low confidence lookup

Execution 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 lookup
cve · low confidence lookup

CVE-2022-43467 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-43467Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Open BabelOpen Babel3.1.1, master commit 530dbfa3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-119 · source CWE mapping

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.