CVE-2024-56073VulnerabilityPublished 15 Dec 2024Updated 16 Dec 2024

CVE-2024-56073: fastnetmon · n/a

Affects fastnetmonSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.2.8 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

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

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

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

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

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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

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

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

Upgrade pavel-odintsov/fastnetmon to 1.2.8.

Affected software

Product	Affected	Fixed in
GitHubpavel-odintsov/fastnetmon`pkg:github/pavel-odintsov/fastnetmon`Other threats	Affected <1.2.8	Fixed in 1.2.8

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

AI-suggested

1. Upgrade FastNetMon to a version that addresses this vulnerability once an official patch is released. 2. Implement network-level filtering to block or restrict Netflow v9 traffic from untrusted or external sources, reducing exposure to crafted packets. 3. Deploy intrusion detection or prevention systems (IDS/IPS) with signatures or anomaly detection rules to identify and block malformed Netflow v9 templates. 4. Isolate FastNetMon instances within secure network segments to limit access to trusted monitoring infrastructure only. 5. Regularly audit and monitor FastNetMon logs and system health to detect abnormal crashes or service interruptions promptly. 6. Consider fallback or redundancy mechanisms for network monitoring to maintain visibility during FastNetMon outages. 7. Engage with the FastNetMon community or support channels to obtain early access to patches or workarounds. 8. If immediate patching is not possible, temporarily disable Netflow v9 processing or limit the acceptance of Netflow data to trusted sources only, if configurable.

Description

An issue was discovered in FastNetMon Community Edition through 1.2.7. Zero-length templates for Netflow v9 allow remote attackers to cause a denial of service (divide-by-zero error and application crash).

Impact

The primary impact of CVE-2024-56073 is a denial of service condition that disrupts the availability of FastNetMon's network monitoring capabilities. Organizations using FastNetMon for DDoS detection and network traffic analysis may experience service outages, reducing their visibility into network traffic and potentially delaying detection and mitigation of actual attacks. This can increase the risk of undetected network intrusions or prolonged DDoS attacks. Since the vulnerability does not affect confidentiality or integrity, data breaches or unauthorized data modification are not direct concerns. However, the loss of monitoring capability can indirectly increase overall security risk. The ease of remote exploitation without authentication means attackers can trigger the DoS from anywhere on the network, including potentially the internet if the service is exposed. This could be leveraged by threat actors to degrade network defenses or as part of a multi-stage attack. The lack of known exploits in the wild suggests limited current exploitation but also highlights the need for proactive mitigation before attackers develop weaponized exploits.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 23:55 UTC

WeaknessesCWE-369

Technical details

References

Community reviews

Related threats