CVE-2023-48693 — Azure RTOS ThreadX Remote Code Execution Vulnerability

Azure RTOS ThreadX is an advanced real-time operating system (RTOS) designed specifically for deeply embedded applications. An attacker can cause arbitrary read and write due to vulnerability in parameter checking mechanism in Azure RTOS ThreadX, which may lead to privilege escalation. The affected components include RTOS ThreadX v6.2.1 and below. The fixes have been included in ThreadX release 6.3.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Published Dec 5, 2023Updated Aug 2, 2024Sources: cvelistV5, GitHub_M

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

chance of exploitation in 30 days

Affects

azure rtos

threadx

CVSS base

8.7

HIGH

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.

Vendors (1)

azure rtos

Products (1)

threadx

Every base score collected

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

Score	Version	Severity	Expl.	Impact	Source
8.7	CVSS 3.1	HIGH	—	—	cvelistV5

Weakness & attack patterns

CWE-20

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

T1562.003Impair Defenses: Impair Command History Logging
T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable

References

1 on the record

github.com/azure-rtos/threadx/security/advisories/GHSA-p7w6-62rq-vrf9
x_refsource_CONFIRM

Elsewhere on this site

azure rtosevery CVE for this vendor
CWE-20other pages naming this weakness

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.