CVE-2024-0887VulnerabilityPublished 25 Jan 2024Updated 29 May 2025

CVE-2024-0887: Mafiatic Blue Server · Denial of Service

Affects Mafiatic Blue ServerSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 1.1% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jan 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 2026-10-25.

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
Mafiatic Blue Server	Affected =1.1	Fixed in–

AI-suggested

Given the lack of an official patch, European organizations should implement network-level protections such as firewall rules to restrict access to the Mafiatic Blue Server’s connection ports only to trusted IP addresses or internal networks. Deploying intrusion detection and prevention systems (IDS/IPS) configured to detect anomalous traffic patterns targeting the connection handler could help identify and block exploitation attempts. Rate limiting incoming connections and implementing connection throttling can reduce the risk of resource exhaustion. Organizations should also monitor server logs and performance metrics closely for signs of unusual connection spikes or crashes. If possible, isolating the vulnerable server in a segmented network zone with limited exposure to the internet will reduce attack vectors. Planning for rapid incident response and service failover can mitigate operational impact if an attack occurs. Finally, organizations should maintain communication with the vendor for updates and apply patches promptly once available.

Description

A vulnerability, which was classified as problematic, has been found in Mafiatic Blue Server 1.1. Affected by this issue is some unknown functionality of the component Connection Handler. The manipulation leads to denial of service. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-252038 is the identifier assigned to this vulnerability.

Impact

For European organizations using Mafiatic Blue Server 1.1, this vulnerability poses a risk of service disruption due to denial of service attacks. The impact is primarily on availability, potentially causing downtime for applications or services relying on this server. This can affect business continuity, customer trust, and operational efficiency, especially for organizations providing critical or real-time services. Since the exploit requires no authentication and can be launched remotely, attackers can easily target exposed servers over the internet. This increases the attack surface for organizations with publicly accessible Mafiatic Blue Server deployments. While no data confidentiality or integrity is directly threatened, the service unavailability could indirectly affect compliance with service-level agreements (SLAs) and regulatory requirements around uptime and incident response. The absence of a patch means organizations must rely on temporary mitigations, increasing operational risk until a fix is available.

CWE-404Improper Resource Shutdown or Release (opens in a new tab)
Class weaknessLikelihood of exploit: Medium
The product does not release or incorrectly releases a resource before it is made available for re-use.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free memory in a function. If you allocate memory that you intend to free upon completion of the function, you must be sure to free the memory at all exit points for that function including error…
Implementation
Memory should be allocated/freed using matching functions such as malloc/free, new/delete, and new[]/delete[].
Attack patterns
TCP Fragmentation (opens in a new tab)
UDP Fragmentation (opens in a new tab)
ICMP Fragmentation (opens in a new tab)
BlueSmacking (opens in a new tab)
Flooding (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 7 Jul 2025, 23:41 UTC

WeaknessesCWE-404

Technical details

References

Community reviews

Related threats