# CVE-2024-35204: Privilege escalation in n/a

> Low-privileged users can escalate privileges due to incorrect folder permissions in Veritas System Recovery.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2024
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-qrj2-26jq-rq86

## What is CVE-2024-35204?

CVE-2024-35204 is a high-severity vulnerability in n/a, published on 13 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-272 (Least Privilege Violation)

## Which versions are affected by CVE-2024-35204?


## How do I fix CVE-2024-35204?

No fix has been published for CVE-2024-35204 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-35204 being exploited?

There is no known exploitation of CVE-2024-35204 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35204 and fix it if it is affected.

What it is: CVE-2024-35204 is a high-severity vulnerability in n/a, published on 13 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-35204 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-35204/ (Markdown: https://insights.sbomify.com/CVE-2024-35204/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-35204
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-35204
- OSV: https://osv.dev/vulnerability/CVE-2024-35204

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-35204/
Summaries are generated and may contain mistakes; the official description above is the record.