Skip to main content
VulnerabilityPublished Updated

CVE-2024-45520: atlant · Out-of-bounds Read

Affects atlantSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 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 43% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Dec 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
Withsecurewithsecure/atlantpkg:deb/withsecure/atlantOther threatsAffected
  • =1.0.35-1
Fixed in–

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

AI-suggested

Until an official patch is released, organizations should implement several practical mitigations to reduce risk from CVE-2024-45520. First, restrict network access to the WithSecure Atlant scanning service to trusted sources only, using firewall rules or network segmentation to limit exposure to untrusted or external inputs. Second, implement strict file upload and transfer controls to prevent untrusted PE32 files from reaching the scanning engine, including sandboxing or pre-scanning with alternative tools. Third, monitor logs and system behavior for signs of crashes or abnormal service restarts that could indicate exploitation attempts. Fourth, consider deploying redundant or failover scanning systems to maintain malware detection capabilities if one instance is disrupted. Fifth, engage with WithSecure support channels to obtain early patch information or workarounds. Finally, maintain up-to-date backups and incident response plans to quickly recover from potential service disruptions. These measures go beyond generic advice by focusing on access control, input validation, monitoring, and operational resilience specific to this vulnerability's characteristics.

Description

WithSecure Atlant (formerly F-Secure Atlant) 1.0.35-1 allows a remote Denial of Service because of memory corruption during scanning of a PE32 file.

References

Community reviews

Loading reviews…