# CVE-2022-46413: Command injection in n/a

> Authenticated attackers can execute arbitrary commands remotely via the management portal of Veritas NetBackup Flex Scale and Access Appliance.

- **Severity:** High 8.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-f4r6-7g3q-rfhw

## What is CVE-2022-46413?

CVE-2022-46413 is a high-severity command injection vulnerability in n/a, published on 4 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Veritas NetBackup Flex Scale through 3.0 and Access Appliance through 8.0.100. Authenticated remote command execution can occur via the management portal.

## Which versions are affected by CVE-2022-46413?

It affects 2 products.


Products: Veritas Access Appliance, Veritas Netbackup Flex Scale Appliance.

## How do I fix CVE-2022-46413?

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

## Is CVE-2022-46413 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-46414](https://insights.sbomify.com/CVE-2022-46414/): Command injection in n/a (critical 9.8)
- [CVE-2022-46411](https://insights.sbomify.com/CVE-2022-46411/): Hardcoded credentials in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46413 and fix it if it is affected.

What it is: CVE-2022-46413 is a high-severity command injection vulnerability in n/a, published on 4 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46413 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-2022-46413/ (Markdown: https://insights.sbomify.com/CVE-2022-46413/index.md)
```

## Sources

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

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