dbcve.org
Linux ProtectionApplication · F Secure

CVE-2023-43767

HIGH · 7.5 CVSS v3.1 Published 2023-09-22
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 allow Denial of Service via the aepack archive unpack handler. 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, Linux Security 64 12.0 , Linux Protection 12.0, and WithSecure Atlant (formerly F-Secure 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 · moderate confidence

A denial of service vulnerability exists in the aepack archive unpack handler of multiple WithSecure endpoint protection products. A specially crafted aepack archive file can cause the product to become unresponsive or crash, likely due to improper handling during archive decompression or parsing.

MitigationApply vendor-supplied patches or updates to affected WithSecure products when available. Until patches are released, consider restricting processing of aepack archive files or monitoring for anomalous behavior.

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
Linux ProtectionApplication
Affected:= 12.0
Linux Security 64Application
Affected:= 12.0
AtlantApplication
Affected:= 1.0.35-1
Client SecurityApplication
Affected:= 15.00
Elements Endpoint ProtectionApplication
Affected:>= 17.0
Email And Server SecurityApplication
Affected:= 15.00
Server SecurityApplication
Affected:= 15.00

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/F-Secure products
    Run system package queries (e.g., dpkg -l, rpm -qa, or similar) or check installed programs list for any of these product names: F-Secure Linux Protection, F-Secure Linux Security 64, F-Secure Atlant, F-Secure Client Security, F-Secure Elements Endpoint Protection, F-Secure Email And Server Security, or F-Secure Server Security
    Affected if Any of the listed WithSecure/F-Secure products are installed on the system
  2. Check product version against affected ranges
    Use the vendor's version query mechanism (such as 'f-secure --version', 'fsavg --version', or the product-specific command for your installed solution) to determine the exact version number, then compare against: 12.0, 1.0.35-1, 15.00, or >=17.0 depending on the product
    Affected if The installed version matches exactly one of the affected version ranges (12.0, 1.0.35-1, 15.00, or >=17.0)
  3. Verify aepack archive processing is enabled
    Check the product configuration or settings for any options related to archive scanning, aepack handling, or archive decompression. Look for settings like 'scan archives', 'archive scanning', 'aepack support', or similar in the product's configuration files or management interface
    Affected if Aepack archive processing or archive scanning is enabled in the product settings
  4. Confirm the product includes the vulnerable unpack handler
    Review the product's feature list, modules, or component inventory to verify the aepack archive unpack handler component is present. This may be listed as part of the scanning engine, archive handler, or real-time protection module
    Affected if The aepack archive unpack handler component is installed as part of the protection product

You are affected if a WithSecure/F-Secure product from the list is installed with a version matching 12.0, 1.0.35-1, 15.00, or >=17.0 AND aepack archive processing is enabled in the product configuration.

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-supplied patches or updates to affected WithSecure products when available. Until patches are released, consider restricting processing of aepack archive files or monitoring for anomalous behavior.

Fix this in Linux Protection Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-43767 — 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-43767 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