CVE-2024-45520
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWithSecure 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceWithSecure Atlant (formerly F-Secure Atlant) versions 1.0.35-1 contains a memory corruption vulnerability in its file scanning engine. When the antivirus product scans a specially crafted malicious PE32 (Portable Executable 32-bit) file, the memory corruption is triggered, causing the software to crash and resulting in a remote denial of service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm WithSecure Atlant is installedCheck for Atlant installation using system package manager, or look for Atlant executable/process (e.g., 'atlant.exe', 'fs atlant' or 'withsecure atlant' in installed programs)Affected if WithSecure Atlant is not installed on the system - user is not affected
-
Identify installed Atlant versionRun command to retrieve version: 'atlant --version', check Windows registry under HKLM\Software\WithSecure\Atlant\, or view version info in Add/Remove ProgramsAffected if Installed version is 1.0.35 or higher but below any patched version - user may be affected; versions below 1.0.35 are not in the affected range
-
Verify file scanning engine is enabledCheck Atlant configuration for real-time or on-demand scanning status, typically via Atlant management console, config file, or registry key related to scanning serviceAffected if Scanning engine is active and processes PE32 files - user is affected if version is in vulnerable range
-
Confirm PE32 scanning is permittedReview file type scanning settings in Atlant to ensure PE32/PE executable scanning is not excluded or disabledAffected if PE32 file scanning is enabled and version is 1.0.35-1 - user is vulnerable to the memory corruption trigger
-
Check for recent Atlant crash eventsReview Windows Event Viewer Application logs, Atlant crash/dump logs, or system event logs around time of PE32 file scans for Atlant process failuresAffected if Atlant crashes occurred after scanning PE32 files and version is in affected range - indicates active exploitation of this vulnerability
User is affected if WithSecure Atlant version 1.0.35 or higher is installed with the file scanning engine and PE32 scanning enabled, and the software has crashed after processing malicious PE32 files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-supplied security update for WithSecure Atlant when available. Until patched, consider network-based filtering or sandboxing of untrusted PE32 files before they reach the Atlant scanning engine to reduce exposure.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45520 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45520 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data