# CVE-2022-46892: Security feature bypass in n/a

> Improper access controls in Ampere Altra firmware allow the OS to reinitialize a disabled root complex, bypassing security restrictions.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2023
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-2mmc-97mx-9r37

## What is CVE-2022-46892?

CVE-2022-46892 is a critical vulnerability in n/a, published on 15 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Ampere AltraMax and Ampere Altra before 2.10c, improper access controls allows the OS to reinitialize a disabled root complex.

Weakness: CWE-284 (Improper Access Control)

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

It affects 2 products.


Products: Amperecomputing Ampere Altra Firmware, Amperecomputing Ampere Altra Max Firmware.

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

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

## Is CVE-2022-46892 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-32295](https://insights.sbomify.com/CVE-2022-32295/): Security feature bypass in n/a (critical 9.8)
- [CVE-2022-37459](https://insights.sbomify.com/CVE-2022-37459/): Other in n/a (high 7.8)
- [CVE-2021-45454](https://insights.sbomify.com/CVE-2021-45454/): Information disclosure in n/a (high 7.5)
- [CVE-2022-35888](https://insights.sbomify.com/CVE-2022-35888/): Information disclosure in n/a (medium 6.5)
- [CVE-2022-25368](https://insights.sbomify.com/CVE-2022-25368/): Information disclosure in n/a (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46892 is a critical vulnerability in n/a, published on 15 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46892 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-46892/ (Markdown: https://insights.sbomify.com/CVE-2022-46892/index.md)
```

## Sources

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

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