# CVE-2024-34404: Missing authorization in n/a

> NetBackup administrators can bypass retention lock controls to prematurely delete backup images, compromising data integrity and availability.

- **Severity:** Medium 6.8 (`CVSS:3.1/AC:L/AV:N/A:N/C:N/I:H/PR:H/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-6q28-4fqw-89m2

## What is CVE-2024-34404?

CVE-2024-34404 is a medium-severity missing authorization vulnerability in n/a, published on 3 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was discovered in the Alta Recovery Vault feature of Veritas NetBackup before 10.4 and NetBackup Appliance before 5.4. By design, only the cloud administrator should be able to disable the retention lock of Governance mode images. This vulnerability allowed a NetBackup administrator to modify the expiration of backups under Governance mode (which could cause premature deletion).

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2024-34404 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34404 is a medium-severity missing authorization vulnerability in n/a, published on 3 May 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-34404 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-34404/ (Markdown: https://insights.sbomify.com/CVE-2024-34404/index.md)
```

## Sources

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

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