Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-55560: n/a

0
Critical
VulnerabilityCVE-2024-55560cvecve-2024-55560
Published: Sun Dec 08 2024 (12/08/2024, 00:00:00 UTC)
Source: CVE Database V5

Description

MailCleaner before 28d913e has default values of ssh_host_dsa_key, ssh_host_rsa_key, and ssh_host_ed25519_key that persist after installation.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 23:54:38 UTC

Technical Analysis

CVE-2024-55560 identifies a critical security vulnerability in MailCleaner, an email security gateway product, affecting versions prior to the commit identified as 28d913e. The core issue is that the software installs with default SSH host keys—specifically ssh_host_dsa_key, ssh_host_rsa_key, and ssh_host_ed25519_key—that remain unchanged after installation. These default keys are likely publicly known or easily obtainable, which undermines the cryptographic trust model of SSH connections to the MailCleaner server. An attacker with network access can exploit this by performing man-in-the-middle (MITM) attacks, impersonating the MailCleaner server, or decrypting SSH traffic, thereby compromising confidentiality and integrity of communications. The vulnerability is remotely exploitable over the network without any authentication or user interaction, as indicated by the CVSS vector AV:N/AC:L/PR:N/UI:N. The CVSS score of 9.8 reflects the critical nature of this flaw, impacting confidentiality, integrity, and availability (C:H/I:H/A:H). Although no known exploits have been reported in the wild yet, the ease of exploitation and severity make this a high-priority issue. The vulnerability affects all installations using the default keys, which is a common scenario if administrators do not manually regenerate SSH host keys post-installation. The absence of patch links suggests that users should update to versions including the commit 28d913e or later, where this issue is resolved by regenerating unique SSH host keys during setup. This vulnerability highlights the importance of unique cryptographic key generation in security appliances to prevent impersonation and MITM attacks.

Potential Impact

The impact of CVE-2024-55560 is severe for organizations relying on MailCleaner for email security. Attackers exploiting this vulnerability can impersonate the MailCleaner server, intercept or alter email traffic, and potentially gain unauthorized access to internal networks. This compromises the confidentiality and integrity of sensitive communications and can lead to further lateral movement within the network. The availability of the service may also be disrupted if attackers manipulate SSH connections or credentials. Given the critical CVSS score and the lack of required authentication, the vulnerability poses a significant risk to organizations’ email infrastructure, potentially enabling espionage, data breaches, and service outages. The threat is especially acute for enterprises, government agencies, and service providers that depend on MailCleaner for filtering and securing email traffic. Without timely mitigation, attackers could leverage this vulnerability to undermine trust in secure communications and gain footholds for broader attacks.

Mitigation Recommendations

To mitigate CVE-2024-55560, organizations should immediately verify if their MailCleaner installations are using default SSH host keys. Administrators must regenerate SSH host keys (DSA, RSA, ED25519) to unique values immediately after installation or upgrade. This can typically be done by deleting the existing default keys and running the SSH key generation commands (e.g., ssh-keygen) on the MailCleaner server. Additionally, upgrading MailCleaner to the version including commit 28d913e or later is critical, as this update ensures default keys are not reused. Network administrators should also monitor SSH connections to MailCleaner servers for anomalies indicative of MITM attacks. Implementing strict SSH host key verification policies and using out-of-band methods to verify host keys can further reduce risk. Finally, organizations should audit their email security infrastructure regularly to detect any signs of compromise related to this vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2024-12-08T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6bd0b7ef31ef0b55b283

Added to database: 2/25/2026, 9:38:24 PM

Last enriched: 2/27/2026, 11:54:38 PM

Last updated: 4/12/2026, 1:52:34 AM

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses