Mina SshdApplication · Apache
CVE-2024-41909
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 · uneditedLike many other SSH implementations, Apache MINA SSHD suffered from the issue that is more widely known as CVE-2023-48795. An attacker that can intercept traffic between client and server could drop certain packets from the stream, potentially causing client and server to consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack The mitigations to prevent this type of attack were implemented in Apache MINA SSHD 2.12.0, both client and server side. Users are recommended to upgrade to at least this version. Note that both the client and the server implementation must have mitigations applied against this issue, otherwise the connection may still be affected.
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 confidenceApache MINA SSHD contained the Terrapin attack vulnerability (CVE-2023-48795) where a man-in-the-middle attacker intercepting SSH traffic could drop packets to cause client and server to negotiate a connection with downgraded or disabled security features. This affects the SSH implementation's strict key exchange algorithms.
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
Mina SshdApplication
<= 2.11.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Mina Sshd library versionCheck your project's dependency management file (pom.xml for Maven, build.gradle for Gradle, or similar) for the Apache Mina Sshd artifact version, or run 'jar -tf' on the sshd-core jar to read the manifest file for the Implementation-Version attributeAffected if The version listed is 2.11.0 or lower
-
Confirm SSH functionality is in useReview your application code or deployment to verify that Apache Mina Sshd classes (org.apache.sshd.*) are being used to provide SSH server or client capabilitiesAffected if Your application uses Apache Mina Sshd for SSH connections (either as server, client, or both)
-
Check for active SSH connections using strict key exchangeReview your SSH server or client configuration for the 'strictkex' property or key exchange algorithm (kex) settings. If running, inspect active connections or logs for the key exchange algorithms in useAffected if SSH connections are established using key exchange algorithms that can be downgraded by an attacker (the default behavior in vulnerable versions)
You are affected if your application uses Apache Mina Sshd version 2.11.0 or earlier for SSH connections and accepts connections that could be subject to man-in-the-middle packet manipulation during key exchange.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Apache MINA SSHD to version 2.12.0 or later on both client and server implementations. Both sides must be patched for complete protection.
Apache MINA SSHD 2.12.0 or later
- Identify all systems and applications using Apache MINA SSHD version 2.11.0 or earlier
- Upgrade Apache MINA SSHD to version 2.12.0 or later on both client and server implementations
- Verify the upgrade was successful by checking the version number
- Restart any services using the updated library
- Test SSH connections to ensure normal functionality is maintained after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Mina Sshd
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41909 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-41909 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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