CVE-2024-54662VulnerabilityPublished 17 Dec 2024Updated 18 Dec 2024

CVE-2024-54662: dante · n/a

Affects danteSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical · fixed in 1.4.4 : patch dante as a priority.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.4.4

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Dantedante/dante`pkg:deb/dante/dante`Other threats	Affected =1.4.0 =1.4.1 =1.4.2 =1.4.3	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-54662, organizations should take the following specific actions: 1) Immediately upgrade Dante to version 1.4.4 or later, where the access control issue is resolved. 2) Review and audit sockd.conf configurations, especially the socksmethod directives, to ensure they enforce strict access controls aligned with organizational security policies. 3) Implement network-level restrictions such as firewall rules to limit access to the SOCKS proxy service only to trusted hosts and networks. 4) Monitor proxy logs for unusual or unauthorized connection attempts that could indicate exploitation attempts. 5) Employ intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics tuned to detect anomalous SOCKS proxy activity. 6) Consider isolating the proxy server in a segmented network zone to reduce potential lateral movement if compromised. 7) Educate administrators on secure configuration best practices for Dante and regularly verify compliance. These targeted steps go beyond generic patching advice by emphasizing configuration review, network controls, and monitoring to reduce exposure and detect exploitation attempts.

Description

Dante 1.4.0 through 1.4.3 (fixed in 1.4.4) has incorrect access control for some sockd.conf configurations involving socksmethod.

Impact

The impact of CVE-2024-54662 is substantial for organizations using affected versions of Dante as a SOCKS proxy server. Successful exploitation allows unauthenticated remote attackers to bypass access controls, potentially gaining unauthorized access to internal network resources or sensitive data transmitted through the proxy. This can lead to confidentiality breaches, such as interception of sensitive communications, and integrity violations, including manipulation of data or proxy configurations. The vulnerability does not directly affect availability but can facilitate further attacks, such as lateral movement or data exfiltration. Organizations in sectors with stringent data privacy requirements or critical infrastructure relying on Dante proxies are at heightened risk. The ease of exploitation without authentication or user interaction increases the threat level, making it attractive for attackers. Although no known exploits are currently in the wild, the vulnerability's critical severity necessitates immediate attention to prevent potential compromise.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 03:21 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats