dbcve.org
Client SecurityApplication · Withsecure

CVE-2023-47264

HIGH · 7.5 CVSS v3.1 Published 2023-11-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Certain WithSecure products have a buffer over-read whereby processing certain fuzz file types may cause a denial of service (DoS). 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 (formerly F-Secure Atlant) 15 and later.

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 confidence

A buffer over-read vulnerability exists in WithSecure products when processing certain fuzzed file types. The vulnerability occurs during file parsing/scanning operations, allowing an attacker to trigger a denial of service by providing specially crafted files that cause the software to read beyond buffer boundaries.

MitigationApply vendor patches for affected WithSecure products (Client Security 15, Server Security 15, Email and Server Security 15, Elements Endpoint Protection 17+, Linux Security 64 12.0, Linux Protection 12.0, and Atlant 15+). Until patches are available, consider disabling or restricting file scanning for unknown/untrusted fuzz file types.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Client SecurityApplication
Affected:= 15
Elements Endpoint ProtectionApplication
Affected:>= 17
Email And Server SecurityApplication
Affected:= 15
Server SecurityApplication
Affected:= 15
Linux ProtectionApplication
Affected:= 12.0
Linux Security 64Application
Affected:= 12.0
AtlantApplication
Affected:>= 15.0= 1.0.35-1

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed WithSecure product
    Check for presence of WithSecure security software on the system. Look for process names such as 'fsp.exe', 'fsma', 'fsdaemon', or service entries for WithSecure products. On Linux, check for 'withsecure' or 'fsdaemon' processes or services.
    Affected if No WithSecure product is found on the system.
  2. Determine product name and version
    Identify the specific WithSecure product installed and its exact version number. Common locations include: Windows registry under HKLM\Software\WithSecure or HKLM\Software\F-Secure; on Linux check /opt/f-secure or /opt/withsecure directories for version files, or run 'rpm -qi f-secure' or 'dpkg -l f-secure' if applicable.
    Affected if Unable to determine product name or version.
  3. Compare version against affected ranges
    Match the installed product and version against the affected list: Client Security = 15, Elements Endpoint Protection >= 17, Email And Server Security = 15, Server Security = 15, Linux Protection = 12.0, Linux Security 64 = 12.0, Atlant >= 15.0 or = 1.0.35-1. The '=' means exact version, '>=' means that version or later.
    Affected if The installed version is NOT in the affected list.
  4. Confirm file scanning is enabled
    Check if real-time file scanning or on-demand scanning functionality is active. This is typically the primary function of endpoint protection products. Look for scanning-related services running, or check the product console for scanning status. On Windows, the real-time protection is often called 'Real-time scanning' or 'On-access scanning'.
    Affected if File scanning is disabled or not present on the system.

The system is affected if a WithSecure product is installed with an affected version AND file scanning functionality is enabled, as the buffer over-read triggers during file parsing operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for affected WithSecure products (Client Security 15, Server Security 15, Email and Server Security 15, Elements Endpoint Protection 17+, Linux Security 64 12.0, Linux Protection 12.0, and Atlant 15+). Until patches are available, consider disabling or restricting file scanning for unknown/untrusted fuzz file types.

Fix this in Client Security Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47264 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47264 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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