dbcve.org
Elements Endpoint Detection And ResponseApplication · F Secure

CVE-2022-28887

HIGH · 7.5 CVSS v3.1 Published 2022-10-12
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
Multiple Denial-of-Service (DoS) vulnerability was discovered in F-Secure & WithSecure products whereby the aerdl.dll unpacker handler function crashes. This can lead to a possible scanning engine crash.

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 F-Secure and WithSecure antivirus products within the aerdl.dll unpacker handler function. When processing specially crafted files, the unpacker handler crashes, causing the entire scanning engine to fail. This can be triggered remotely during file scanning operations.

MitigationApply the vendor-supplied security update or upgrade to a patched version of the F-Secure/WithSecure product to remediate this vulnerability.

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
Elements Endpoint Detection And ResponseApplication
Affected:all versions
Elements Endpoint ProtectionApplication
Affected:all versions
AtlantApplication
Affected:all versions
Internet GatekeeperApplication
Affected:all versions
Linux SecurityApplication
Affected:all versions
Linux Security 64Application
Affected:all versions

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 F-Secure or WithSecure products
    Check the system for installed antivirus/security products. On Windows, review installed programs in Control Panel or use 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName' in PowerShell. On Linux, check package manager listings for f-secure, withsecure, or elements packages.
    Affected if Any of the following products appear: F-Secure Elements Endpoint Detection And Response, F-Secure Elements Endpoint Protection, F-Secure Atlant, F-Secure Internet Gatekeeper, F-Secure Linux Security, or F-Secure Linux Security 64.
  2. Locate the aerdl.dll component
    Search for aerdl.dll on the system. Common locations include C:\Program Files\F-Secure\ or C:\Program Files\WithSecure\ directories on Windows, or /opt/f-secure/ or /opt/withsecure/ on Linux. Use 'dir /s C:\*aerdl.dll' on Windows or 'find / -name aerdl.dll 2>/dev/null' on Linux.
    Affected if The file aerdl.dll exists in any F-Secure or WithSecure product directory.
  3. Confirm the scanning engine is active
    Verify the real-time scanning or on-demand scanner service is running. On Windows, check the F-Secure service status via Services.msc or 'sc query f-secure'. On Linux, check for running processes like 'fsspamd' or 'f-secure' daemons.
    Affected if The F-Secure scanning engine service or daemon is running on the system.
  4. Verify the vulnerability trigger condition
    This vulnerability is triggered during file scanning operations when the aerdl.dll unpacker processes specially crafted archive files. The crash causes the scanning engine to fail. Test by scanning a potentially malicious archive file or reviewing crash logs in the F-Secure product logs directory.
    Affected if The scanning engine crashes or becomes unavailable during archive file processing, indicating the vulnerability is present.

If any F-Secure or WithSecure product from the affected list is installed with the aerdl.dll component and the scanning engine is active, the environment is vulnerable to CVE-2022-28887.

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 the vendor-supplied security update or upgrade to a patched version of the F-Secure/WithSecure product to remediate this vulnerability.

Fix this in Elements Endpoint Detection And Response Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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