# CVE-2022-28622: Weak cryptography in HPE StoreOnce Software

> Weak SSH key exchange algorithms in HPE StoreOnce Software allow remote attackers to bypass security controls and potentially gain unauthorized access.

- **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:** 27 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6hj7-83x8-pjqq

## What is CVE-2022-28622?

CVE-2022-28622 is a high-severity vulnerability in HPE StoreOnce Software, published on 27 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A potential security vulnerability has been identified in HPE StoreOnce Software. The SSH server supports weak key exchange algorithms which could lead to remote unauthorized access. HPE has made the following software update to resolve the vulnerability in HPE StoreOnce Software 4.3.2.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Hpe Storeonce 3640 Firmware.

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

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

## Is CVE-2022-28622 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28622 is a high-severity vulnerability in HPE StoreOnce Software, published on 27 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-28622 in the wild and no public exploit code.

Affected product: HPE StoreOnce Software. 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-28622/ (Markdown: https://insights.sbomify.com/CVE-2022-28622/index.md)
```

## Sources

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

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