# CVE-2023-30905: Misconfiguration in HPE MC990 X RMC firmware

> Inadequate default configuration in HPE RMC firmware allows attackers to obtain enhanced privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2023
- **Updated:** 17 Dec 2024
- **Also known as:** GHSA-rw94-xc46-wxfw

## What is CVE-2023-30905?

CVE-2023-30905 is a high-severity vulnerability in Hewlett Packard Enterprise (HPE) HPE MC990 X RMC firmware, published on 16 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The MC990 X and UV300 RMC component has and inadequate default configuration that could be exploited to obtain enhanced privilege.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2023-30905?

It affects 2 products.


Products: Hpe Integrity Mc990 X Server Rmc Firmware, Hpe Sgi Uv 300 Rmc Firmware.

## How do I fix CVE-2023-30905?

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

## Is CVE-2023-30905 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30905 and fix it if it is affected.

What it is: CVE-2023-30905 is a high-severity vulnerability in Hewlett Packard Enterprise (HPE) HPE MC990 X RMC firmware, published on 16 Jun 2023. 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-2023-30905 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise (HPE) HPE MC990 X RMC firmware. 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-2023-30905/ (Markdown: https://insights.sbomify.com/CVE-2023-30905/index.md)
```

## Sources

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

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