dbcve.org
Ipworks SshApplication · Nsoftware

CVE-2024-6580

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
The /n software IPWorks SSH library SFTPServer component can be induced to make unintended filesystem or network path requests when loading a SSH public key or certificate. To be exploitable, an application calling the SFTPServer component must grant user access without verifying the SSH public key or certificate (which would most likely be a separate vulnerability in the calling application). IPWorks SSH versions 22.0.8945 and 24.0.8945 were released to address this condition by blocking all filesystem and network path requests for SSH public keys or certificates.

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

The SFTPServer component in /n software IPWorks SSH library can be induced to make unintended filesystem or network path requests when loading SSH public keys or certificates. Exploitation requires an application using SFTPServer to grant user access without proper SSH public key or certificate validation—a separate vulnerability in the calling application. Versions 22.0.8945 and 24.0.8945 block all filesystem and network path requests for SSH public keys/certificates.

MitigationUpdate IPWorks SSH library to version 22.0.8945 or 24.0.8945 to block path requests during SSH key/certificate loading. Additionally, ensure the calling application properly validates SSH public keys or certificates before granting access, as this is a prerequisite condition for exploitation.

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
Ipworks SshApplication
Affected:= 22.0.8945= 24.0.8945

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify IPWorks SSH library version
    Check the version of the /n software IPWorks SSH library installed in your application or system. This is typically found in the product's documentation, assembly info, or package manager if using a NuGet/package version. Look for version numbers like 22.0.x.x or 24.0.x.x or earlier.
    Affected if The installed version is earlier than 22.0.8945 or earlier than 24.0.8945 (e.g., 21.x.x, 20.x.x, etc.)
  2. Verify SFTPServer is in use
    Identify if your application uses the SFTPServer component from the IPWorks SSH library. Search your codebase or dependencies for references to SFTPServer, IPWorks SSH, or /n software SSH components.
    Affected if Your application uses the SFTPServer component from a vulnerable version of the library
  3. Check if SSH public key or certificate loading is configured
    Inspect your application's SFTPServer configuration to determine if it is configured to load SSH public keys or certificates from external sources. Look for properties or settings related to SSH key/certificate paths, key files, or certificate files.
    Affected if The SFTPServer is configured to load SSH public keys or certificates from configurable file or network paths
  4. Verify user access validation implementation
    Review the application code that handles SSH public key or certificate validation before granting user access. Determine if the calling application performs proper validation of keys/certificates before allowing access.
    Affected if The application grants user access without proper SSH public key or certificate validation, or uses a custom validation method that does not verify key/certificate integrity

You are affected if you are using a version of IPWorks SSH library earlier than 22.0.8945 or 24.0.8945, your application uses SFTPServer to load SSH public keys or certificates, and the calling application grants access without proper key/certificate validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update IPWorks SSH library to version 22.0.8945 or 24.0.8945 to block path requests during SSH key/certificate loading. Additionally, ensure the calling application properly validates SSH public keys or certificates before granting access, as this is a prerequisite condition for exploitation.

Recommended fix High confidence

IPWorks SSH 22.0.8945 or 24.0.8945 (or later)

  1. 1. Identify the current version of IPWorks SSH library in use
  2. 2. Download and install IPWorks SSH version 22.0.8945 or version 24.0.8945 (or later) from www.nsoftware.com
  3. 3. Rebuild and redeploy any application using the SFTPServer component
  4. 4. Verify that SSH public key/certificate validation is properly implemented in the calling application

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

Fix this in Ipworks Ssh Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6580 — 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-2024-6580 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