dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-54662

CRITICAL · 9.1 CVSS v3.1 Published 2024-12-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Dante 1.4.0 through 1.4.3 (fixed in 1.4.4) has incorrect access control for some sockd.conf configurations involving socksmethod.

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

Dante SOCKS proxy server versions 1.4.0 through 1.4.3 contain an incorrect access control vulnerability affecting certain sockd.conf configurations that use the socksmethod directive. The flaw allows potential unauthorized access to the proxy service, likely due to improper validation of access control rules when socksmethod is configured, resulting in a critical 9.1 CVSS score.

MitigationUpgrade to Dante version 1.4.4. Review and audit existing sockd.conf access control rules and socksmethod configurations to ensure proper authentication and authorization are enforced after the upgrade.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

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

  1. Determine installed Dante version
    Run 'sockd -v' or check the package manager for the installed Dante version
    Affected if Version is 1.4.0, 1.4.1, 1.4.2, or 1.4.3 (versions 1.4.0 through 1.4.3 are affected)
  2. Locate the Dante configuration file
    Find the sockd.conf file - typically in /etc/, /etc/sockd/, or the directory where Dante was configured during installation
    Affected if The sockd.conf file exists and uses the socksmethod directive
  3. Inspect socksmethod directive configuration
    Open sockd.conf and locate any 'socksmethod' or 'socks method' directive lines. Check if they are configured in a way that allows unauthenticated or improperly authenticated access
    Affected if The socksmethod directive is set to a configuration that can be bypassed or allows unauthorized access rules
  4. Review access control rules
    In sockd.conf, examine the 'client' and 'socks' blocks that define who can connect. Look for any permit rules that may be improperly scoped due to the socksmethod misconfiguration
    Affected if Access control rules exist but may be bypassed due to incorrect socksmethod configuration
  5. Test proxy access from an untrusted source
    Attempt to connect to the SOCKS proxy from a host IP address that should be denied according to your access control rules
    Affected if An untrusted or blocked source can successfully connect and relay traffic through the proxy (indicating the bypass is active)

You are affected if Dante version is 1.4.0-1.4.3 AND your sockd.conf uses the socksmethod directive in a configuration that can be exploited to bypass access restrictions.

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 to Dante version 1.4.4. Review and audit existing sockd.conf access control rules and socksmethod configurations to ensure proper authentication and authorization are enforced after the upgrade.

Recommended fix High confidence

1.4.4

  1. Verify current Dante version using 'dante -V' or checking the installed package
  2. Obtain Dante version 1.4.4 from the official Dante project (www.inet.no) or your distribution's package repository
  3. Upgrade Dante to version 1.4.4 using your system's package manager (e.g., apt-get, yum, dnf, or compile from source)
  4. After upgrading, restart the Dante socks daemon (sockd)
  5. Verify the new version is running: 'dante -V' or check the daemon process
  6. Review sockd.conf to ensure the socksmethod configuration is correct for your security requirements

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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