CVE Intelligence
Skip to main content
HIGH

CVE-2024-35204

CVE-2024-35204 Vulnerability Analysis & Exploit Intelligence

Veritas System Recovery before 23.3_Hotfix has incorrect permissions for the Veritas System Recovery folder, and thus low-privileged users can conduct attacks.

Published Updated Sources: cvelistV5, mitre

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

0%

chance of exploitation in 30 days

Affects

veritas

system_recovery

CVSS base

8.4

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)

veritas

Products (1)

system recovery

Every base score collected

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

ScoreVersionSeverityExpl.ImpactSource
8.4CVSS 3.1HIGH——cvelistV5

Weakness & attack patterns

  • CWE-272

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

  • T1574.005Hijack Execution Flow: Executable Installer File Permissions Weakness
  • T1574.010Hijack Execution Flow: Services File Permissions Weakness
  • T1027.006Obfuscated Files or Information: HTML Smuggling

References

1 on the record

Elsewhere on this site

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