CVE Intelligence
Skip to main content
HIGHpublic exploit

CVE-2024-10930

CVE-2024-10930 — Carrier Block Load Privilege Escalation

An Uncontrolled Search Path Element vulnerability exists which could allow a malicious actor to perform DLL hijacking and execute arbitrary code with escalated privileges.

Published Updated Sources: cvelistV5, Carrier

Triage

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

Exploitation

Exploit code

public exploit, none observed

EPSS

0%

chance of exploitation in 30 days

Affects

carrier

block_load

CVSS base

7.1

HIGH

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

Total

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.

Vendors (1)

carrier

Products (1)

block load

Every base score collected

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

ScoreVersionSeverityExpl.ImpactSource
7.1CVSS 4.0HIGH——cvelistV5

Weakness & attack patterns

  • CWE-427

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

  • T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable
  • T1574.009Hijack Execution Flow: Path Interception by Unquoted Path
  • T1574.001Hijack Execution Flow: DLL search order hijacking

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Indexed by

poc in github

References

2 on the record

Elsewhere on this site

  • carrierevery CVE for this vendor
  • CWE-427other 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.