Storeonce 3640 FirmwareOperating system · Hpe

CVE-2022-28622

HIGH · 7.5 CVSS v3.1 Published 2022-06-27
Fix available
A fix is available. Upgrade to 4.3.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

HPE StoreOnce Software SSH server implements weak key exchange algorithms (KEX) that could allow an attacker to force the use of compromised cryptographic primitives, potentially enabling remote unauthorized access to the system.

MitigationUpdate to HPE StoreOnce Software 4.3.2 which contains the patched SSH server with strong key exchange algorithms enabled.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Storeonce 3640 FirmwareOperating system
Affected:< 4.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm HPE StoreOnce 3640 model
    Identify if the system is an HPE StoreOnce 3640 appliance by checking the product model through the system management interface, CLI, or hardware label.
    Affected if The system is not an HPE StoreOnce 3640 model, as this CVE only affects that specific model.
  2. Check installed firmware version
    Access the StoreOnce management interface or use the CLI command to retrieve the current firmware version (typically shown in system info or firmware status).
    Affected if The firmware version is lower than 4.3.2 (for example, 4.2.x, 4.1.x, or earlier).
  3. Verify SSH server is enabled
    Check if the SSH service is enabled and accessible on the StoreOnce system through the management interface or by attempting an SSH connection to the device.
    Affected if SSH server is enabled and reachable on the network, exposing the weak KEX algorithms to potential attackers.
  4. Confirm SSH exposure
    Determine if the SSH port (default 22) is accessible from untrusted networks by reviewing firewall rules or network access lists.
    Affected if The SSH interface is exposed to external or untrusted networks, increasing the risk of exploitation.

The environment is affected if it is an HPE StoreOnce 3640 with firmware version below 4.3.2 and with SSH server enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.3.2 or later
Fixed in 4.3.2
Interim mitigation

Update to HPE StoreOnce Software 4.3.2 which contains the patched SSH server with strong key exchange algorithms enabled.

Recommended fix High confidence

StoreOnce Software 4.3.2

  1. Download HPE StoreOnce Software version 4.3.2 from the HPE support portal (support.hpe.com)
  2. Review the HPE StoreOnce upgrade documentation and release notes
  3. Schedule a maintenance window as firmware updates may require system downtime
  4. Back up current configuration and data
  5. Upload the 4.3.2 firmware to the StoreOnce 3640 device
  6. Follow HPE's documented upgrade procedure to apply the firmware
  7. Verify the upgrade completed successfully
  8. Confirm SSH configuration no longer accepts weak key exchange algorithms

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Storeonce 3640 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28622 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28622 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data