Skip to main content
VulnerabilityPublished Updated

CVE-2024-53426: ntopng · Classic Buffer Overflow

Affects ntopngSource CVE Database V5

0

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
GitHubntop/ntopngpkg:github/ntop/ntopngOther threatsAffected
  • =6.2
Fixed in–

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

AI-suggested

Organizations should implement the following specific mitigations: 1) Restrict local access to systems running ntopng 6.2 to trusted administrators only, using strict access controls and network segmentation to limit exposure. 2) Monitor ntopng processes for crashes or unusual behavior that may indicate exploitation attempts. 3) Regularly check for official patches or updates from ntopng developers addressing CVE-2024-53426 and apply them promptly once available. 4) Consider deploying additional network monitoring tools as redundancy to maintain visibility if ntopng is disrupted. 5) Employ application whitelisting and runtime protections to detect and prevent abnormal memory operations. 6) Conduct internal vulnerability scans and penetration tests focusing on local privilege escalation and memory corruption vectors to identify potential exploitation paths. 7) Educate system administrators about the vulnerability and the importance of minimizing local access and monitoring system stability.

Description

A heap-buffer-overflow vulnerability has been identified in ntopng 6.2 in the Flow::dissectMDNS function.

References

Community reviews

Loading reviews…