# CVE-2022-28621: Information disclosure in HPE NonStop DSM/SCM T6031

> Remote attackers can disclose sensitive information from HPE NonStop DSM/SCM, requiring a software update to mitigate.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-j66x-vhp7-p7xx

## What is CVE-2022-28621?

CVE-2022-28621 is a high-severity vulnerability in HPE NonStop DSM/SCM T6031, published on 28 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote disclosure of sensitive information vulnerability was discovered in HPE NonStop DSM/SCM version: T6031H03^ADP. HPE has provided a software update to resolve this vulnerability in HPE NonStop DSM/SCM.

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

It affects 1 product.


Products: Hpe Nonstop Distributed Systems Management \/ Software Configuration Manager.

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

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

## Is CVE-2022-28621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28621 is a high-severity vulnerability in HPE NonStop DSM/SCM T6031, published on 28 Jun 2022. 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-28621 in the wild and no public exploit code.

Affected product: HPE NonStop DSM/SCM T6031. 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-28621/ (Markdown: https://insights.sbomify.com/CVE-2022-28621/index.md)
```

## Sources

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

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