CVE Intelligence
Skip to main content
LOW

CVE-2023-34994

CVE-2023-34994 Vulnerability Analysis & Exploit Intelligence

An improper resource allocation vulnerability exists in the OAS Engine configuration management functionality of Open Automation Software OAS Platform v18.00.0072. A specially crafted series of network requests can lead to creation of an arbitrary directory. An attacker can send a sequence of requests to trigger this vulnerability.

Published Updated Sources: cvelistV5, talos

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

open automation software

oas_platform

CVSS base

3.1

LOW

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Products (1)

oas platform

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
3.1CVSS 3.1LOW——cvelistV5

Weakness & attack patterns

  • CWE-770

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1498.001Network Denial of Service: Direct Network Flood
  • T1499Endpoint Denial of Service
  • T1499.003Endpoint Denial of Service: Application Exhaustion Flood

References

2 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.