# CVE-2021-32571: Information disclosure in n/a

> Residual files containing credentials remain accessible to privileged accounts during data migration in unsupported Ericsson OSS-RC systems.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2wrc-cg26-jf7m

## What is CVE-2021-32571?

CVE-2021-32571 is a medium-severity vulnerability in n/a, published on 14 Oct 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In OSS-RC systems of the release 18B and older during data migration procedures certain files containing usernames and passwords are left in the system undeleted but in folders accessible by top privileged accounts only. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. Ericsson Network Manager is a new generation OSS system which OSS-RC customers shall upgrade to

Weakness: CWE-459 (Incomplete Cleanup)

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

It affects 1 product.


Products: Ericsson Operations Support System-Radio and Core Firmware.

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

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

## Is CVE-2021-32571 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-32569](https://insights.sbomify.com/CVE-2021-32569/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-32571 is a medium-severity vulnerability in n/a, published on 14 Oct 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-32571 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-32571/ (Markdown: https://insights.sbomify.com/CVE-2021-32571/index.md)
```

## Sources

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

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