dbcve.org
SshdApplication · Apache

CVE-2022-45047

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-16
Fix available
A fix is available. Upgrade to after 2.9.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Class org.apache.sshd.server.keyprovider.SimpleGeneratorHostKeyProvider in Apache MINA SSHD <= 2.9.1 uses Java deserialization to load a serialized java.security.PrivateKey. The class is one of several implementations that an implementor using Apache MINA SSHD can choose for loading the host keys of an SSH server.

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 · high confidence

Apache MINA SSHD's SimpleGeneratorHostKeyProvider class (versions <= 2.9.1) uses unsafe Java deserialization to load serialized java.security.PrivateKey objects. This deserialization of untrusted or potentially tampered key data can be exploited for remote code execution via malicious serialized payloads, as Java deserialization lacks integrity validation by default.

MitigationUpgrade Apache MINA SSHD to a version beyond 2.9.1 that addresses this deserialization flaw, or replace SimpleGeneratorHostKeyProvider with an alternative key provider implementation that does not rely on Java deserialization.

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
SshdApplication
Affected:<= 2.9.1

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
High
Availability
High

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

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. Identify Apache MINA SSHD library version
    Search for sshd-core or sshd dependencies in your project's build files (Maven pom.xml, Gradle build.gradle, or JAR manifest), or list all SSHD-related JARs in your classpath
    Affected if The installed version is 2.9.1 or lower
  2. Locate SimpleGeneratorHostKeyProvider usage
    Search codebase for references to 'SimpleGeneratorHostKeyProvider' in Java source files, configuration files, or XML/JSON config files that set up the SSH server
    Affected if SimpleGeneratorHostKeyProvider class is instantiated or configured as the host key provider
  3. Check host key provider configuration
    Inspect SSH server initialization code or configuration for properties like 'hostKeyProvider', 'keyPath', or 'keyProvider' that specify which provider class handles host keys
    Affected if The configuration explicitly uses SimpleGeneratorHostKeyProvider or its default behavior is relied upon (SimpleGeneratorHostKeyProvider is the default in affected versions)
  4. Inspect key file format
    Examine the host key file referenced in configuration - if it is in the old serialized Java format (often .ser extension or binary format starting with specific bytes), it was likely generated by SimpleGeneratorHostKeyProvider
    Affected if The host key file is stored in serialized Java object format rather than standard OpenSSH key formats (authorized_keys, etc.)

You are affected if you are running Apache MINA SSHD version 2.9.1 or lower AND using SimpleGeneratorHostKeyProvider to load serialized PrivateKey objects as host keys.

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 a release after 2.9.1
Interim mitigation

Upgrade Apache MINA SSHD to a version beyond 2.9.1 that addresses this deserialization flaw, or replace SimpleGeneratorHostKeyProvider with an alternative key provider implementation that does not rely on Java deserialization.

Recommended fix High confidence

Apache MINA SSHD 2.9.2 or later (preferably latest stable such as 2.9.3 or 3.0.0)

  1. 1. Identify all Java projects or applications that depend on Apache MINA SSHD library (org.apache.sshd:sshd-core or similar).
  2. 2. Locate the dependency management file (pom.xml for Maven, build.gradle for Gradle, or similar).
  3. 3. Search for the sshd-core dependency and note the current version (likely <= 2.9.1).
  4. 4. Update the version to 2.9.2 or later (recommended: latest stable release such as 2.9.3 or 3.0.0).
  5. 5. For Maven pom.xml, change the version in the <version> tag, for example: <version>2.9.2</version> to <version>2.9.3</version>.
  6. 6. Rebuild the project to verify the upgrade does not introduce compilation errors.
  7. 7. Test the application to ensure SSH server functionality remains intact after the upgrade.
  8. 8. If using a shaded/uber-jar or bundling SSHD, ensure the bundled library is also updated.
Caveat Minimal risk; this is a patch release fixing a critical security vulnerability. Verify no deprecated API usage if upgrading to major version 3.x.

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

Fix this in Sshd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-45047 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