# CVE-2021-42371: Hardcoded credentials in n/a

> Attackers can exploit hardcoded system account credentials in LPAR2RRD and STOR2RRD to gain unauthorized access and escalate privileges.

- **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:** 8 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-567p-m567-62j8

## What is CVE-2021-42371?

CVE-2021-42371 is a critical vulnerability in n/a, published on 8 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

lpar2rrd is a hardcoded system account in XoruX LPAR2RRD and STOR2RRD before 7.30.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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

It affects 2 products.


Products: Xorux Lpar2rrd, Xorux Stor2rrd.

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

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

## Is CVE-2021-42371 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-24032](https://insights.sbomify.com/CVE-2020-24032/): Command injection in n/a (critical 9.8)
- [CVE-2014-4981](https://insights.sbomify.com/CVE-2014-4981/): Command injection in n/a (critical 9.8)
- [CVE-2014-4982](https://insights.sbomify.com/CVE-2014-4982/): Command injection in n/a (critical 9.8)
- [CVE-2025-54769](https://insights.sbomify.com/CVE-2025-54769/): KL-001-2025-016: Xorux LPAR2RRD File Upload Directory Traversal (high 8.8)
- [CVE-2021-42372](https://insights.sbomify.com/CVE-2021-42372/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-42371 is a critical vulnerability in n/a, published on 8 Nov 2021. 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-2021-42371 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-2021-42371/ (Markdown: https://insights.sbomify.com/CVE-2021-42371/index.md)
```

## Sources

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

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