dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2025-46807

HIGH · 8.7 CVSS v4.0 Published 2025-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
A Allocation of Resources Without Limits or Throttling vulnerability in sslh allows attackers to easily exhaust the file descriptors in sslh and deny legitimate users service.This issue affects sslh before 2.2.4.

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

A file descriptor exhaustion vulnerability in sslh versions before 2.2.4 allows remote attackers to consume all available file descriptors by establishing excessive connections, causing denial of service for legitimate users. The vulnerability stems from inadequate resource limits or throttling on connection handling.

MitigationUpgrade sslh to version 2.2.4 or later to obtain the fix for this resource exhaustion vulnerability.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Check if sslh is installed
    Run 'sslh --version' or check package manager (e.g., 'dpkg -l sslh', 'rpm -qa sslh', 'brew list sslh')
    Affected if sslh is present on the system
  2. Determine the installed sslh version
    Execute 'sslh --version' and note the version number in the output
    Affected if The version is lower than 2.2.4 (e.g., 2.2.3, 2.2.0, 1.x.x)
  3. Verify sslh is network-exposed
    Check sslh configuration file (typically /etc/sslh.cfg, /etc/sslh.conf, or /etc/sslh/sslh.conf) and running processes (ps aux | grep sslh) to confirm it is listening on network interfaces
    Affected if sslh is bound to a reachable network interface (0.0.0.0 or external IP) and accepting connections
  4. Confirm no rate limiting is configured
    Review sslh configuration for any connection throttling, rate limiting, or max-connections settings
    Affected if No resource limits or connection throttling directives are present in the configuration

If sslh is installed with a version before 2.2.4 and is exposed to the network without rate limiting, the environment is vulnerable to file descriptor exhaustion via connection exhaustion.

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

Upgrade sslh to version 2.2.4 or later to obtain the fix for this resource exhaustion vulnerability.

Recommended fix High confidence

sslh version 2.2.4 or later

  1. 1. Check the current installed version of sslh using your package manager or running 'sslh --version'
  2. 2. Upgrade sslh to version 2.2.4 or later. For example, on Debian/Ubuntu: 'apt update && apt install sslh' (or download from source at github.com/yrro/sslh)
  3. 3. Verify the new version is installed: 'sslh --version'
  4. 4. Restart the sslh service to apply the updated binary: 'systemctl restart sslh' or 'service sslh restart'
  5. 5. Verify sslh is running correctly: 'systemctl status sslh' or 'ss -tlnp | grep sslh'

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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