LiveActive security incident?Get immediate response
CVE Record

CVE-2022-42885: A use of uninitialized pointer vulnerability exists in the GRO format res functionality of Open Babel 3.1.1...

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.

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 made to run attacker-controlled code when it processes a specially crafted malformed GRO molecular file. The main business risk is highest where Open Babel is exposed through file upload, automated conversion, or research data pipelines.

Executive priority

Treat as high-priority remediation for internet-facing or partner-facing file-processing workflows. The impact is severe, but urgency depends on whether untrusted GRO files reach Open Babel in your environment.

Technical view

CVE-2022-42885 is a CWE-824 use of uninitialized pointer in Open Babel 3.1.1 and master commit 530dbfa3, specifically in GRO format res functionality. The source description says a malicious malformed file can lead to arbitrary code execution.

Likely exposure

Exposure is likely where Open Babel processes attacker-supplied or externally sourced GRO files, including web services, batch converters, CI research pipelines, and shared scientific workstations. Internal-only desktop use lowers likelihood but not impact.

Exploitation context

The cited record says an attacker can provide a malicious file to trigger the issue. The bundle does not show CISA KEV listing or cited evidence of active exploitation in the wild.

Researcher notes

The CVSS vector is 9.8 with network attack complexity low, but the trigger is file processing. Do not assume exposure unless Open Babel processes attacker-controlled content. No patch detail is provided in the supplied sources.

Mitigation direction

  • Inventory systems and applications using Open Babel 3.1.1 or commit 530dbfa3.
  • Temporarily block untrusted GRO file processing where feasible.
  • Run Open Babel file conversion in isolated, least-privileged sandboxes.
  • Check Open Babel and Talos guidance for fixed versions or vendor mitigations.
  • Monitor file-processing services for crashes or abnormal child process behavior.

Validation and detection

  • Confirm installed Open Babel versions across servers, containers, and workstations.
  • Map all paths where users or partners can submit GRO files.
  • Verify file-processing workers run with minimal privileges and containment.
  • Review logs for recent Open Babel crashes during GRO parsing.
  • Document whether GRO support is business-critical or can be disabled.
Prepared
Confidence
high
Sources
3

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-824: 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-42885 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-42885Attack 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-824 · source CWE mapping

Access of Uninitialized Pointer

Access of Uninitialized Pointer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.