# CVE-2021-26579: Hardcoded credentials in HPE Unified Data Management (UDM)

> Local attackers can disclose privileged information due to hard-coded cryptographic keys in HPE Unified Data Management.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 30 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gx25-hxv6-h79m

## What is CVE-2021-26579?

CVE-2021-26579 is a medium-severity vulnerability in HPE Unified Data Management (UDM), published on 30 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security vulnerability in HPE Unified Data Management (UDM) could allow the local disclosure of privileged information (CWE-321: Use of Hard-coded Cryptographic Key in a product). HPE has provided updates to versions 1.2009.0 and 1.2101.0 of HPE Unified Data Management (UDM). Version 1.2103.0 of HPE Unified Data Management (UDM) removes all hard-coded cryptographic keys.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2021-26579?

It affects 1 product.


Products: Hpe Unified Data Management.

## How do I fix CVE-2021-26579?

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

## Is CVE-2021-26579 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26579 and fix it if it is affected.

What it is: CVE-2021-26579 is a medium-severity vulnerability in HPE Unified Data Management (UDM), published on 30 Mar 2021. 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-2021-26579 in the wild and no public exploit code.

Affected product: HPE Unified Data Management (UDM). 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-2021-26579/ (Markdown: https://insights.sbomify.com/CVE-2021-26579/index.md)
```

## Sources

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

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