CVE-2024-27359
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 · uneditedCertain WithSecure products allow a Denial of Service because the engine scanner can go into an infinite loop when processing an archive file. This affects WithSecure Client Security 15, WithSecure Server Security 15, WithSecure Email and Server Security 15, WithSecure Elements Endpoint Protection 17 and later, WithSecure Client Security for Mac 15, WithSecure Elements Endpoint Protection for Mac 17 and later, WithSecure Linux Security 64 12.0, WithSecure Linux Protection 12.0, and WithSecure Atlant 1.0.35-1.
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 · high confidenceThe WithSecure antivirus engine enters an infinite loop when scanning certain archive files, causing the scanner to become unresponsive and resulting in denial of service. This affects multiple security product lines across client, server, email, and Linux platforms.
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.
-
Identify installed WithSecure productsCheck common installation directories (C:\Program Files\WithSecure, C:\Program Files (x86)\WithSecure on Windows; /opt/f-secure, /opt/withsecure on Linux) and review installed programs list via system package manager or control panelAffected if Any WithSecure security product (Client Security, Server Security, Email Security, or Linux Security) is installed
-
Determine product name and versionQuery the installed WithSecure product for its version: On Windows, check product details in Add/Remove Programs or examine the main executable's version properties; On Linux, run 'rpm -qa | grep -i withsecure' or 'dpkg -l | grep -i withsecure' and note the package versionAffected if The installed version matches or falls within vendor-affected version ranges (compare against WithSecure security advisories for CVE-2024-27359)
-
Verify scanner/archive module is activeConfirm the real-time or on-demand scanner component is enabled. Check product status via the WithSecure client interface, service status (f-secure or withsecure daemons), or configuration policy settings that control archive scanningAffected if The antivirus scanner and archive scanning feature are enabled (this is typically default behavior)
-
Confirm archive processing is usedReview system activity logs or scheduled scan configurations to confirm the product processes or has recently scanned archive files (.zip, .rar, .7z, .tar, .gz, etc.)Affected if The system processes or scans archive files, which triggers the vulnerable code path in the scanning engine
The environment is likely affected if a WithSecure product is installed with an unpatched version and archive scanning is enabled, as processing a specially crafted archive file would trigger the infinite loop in the scanner.
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 vendor-supplied updates/patches for the affected WithSecure products to address the scanner infinite loop vulnerability in archive processing.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27359 — 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-27359 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