dbcve.org
AtlantApplication · F Secure

CVE-2022-28876

HIGH · 7.5 CVSS v3.1 Published 2022-07-14
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
A Denial-of-Service (DoS) vulnerability was discovered in F-Secure Atlant and in certain WithSecure products whereby the scanning the aeheur.dll component can crash the scanning engine. The exploit can be triggered remotely by an attacker.

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 denial-of-service vulnerability exists in F-Secure Atlant and certain WithSecure products where scanning the aeheur.dll heuristic scanning component causes the antivirus scanning engine to crash. The vulnerability can be exploited remotely by an attacker triggering the scan of this specific DLL file.

MitigationApply vendor patches from Fsecure/WithSecure to update the scanning engine to a version that properly handles the aeheur.dll component. As a temporary workaround, consider excluding aeheur.dll from real-time scanning until the patch is applied, though this may reduce heuristic detection capabilities.

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
AtlantApplication
Affected:all versions
Cloud Protection For SalesforceApplication
Affected:all versions
Elements Collaboration ProtectionApplication
Affected:all versions
Internet GatekeeperApplication
Affected:all versions
Linux SecurityApplication
Affected:all versions
Elements Endpoint ProtectionApplication
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 system for installed 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 atlant packages.
    Affected if Any of these products are installed: F-Secure Atlant, F-Secure Cloud Protection for Salesforce, F-Secure Elements Collaboration Protection, F-Secure Internet Gatekeeper, F-Secure Linux Security, or F-Secure Elements Endpoint Protection.
  2. Locate the aeheur.dll component
    Search for aeheur.dll in common F-Secure installation directories: 'C:\Program Files\F-Secure\' on Windows or '/opt/f-secure/' or '/var/opt/f-secure/' on Linux. Use 'dir /s C:\aeheur.dll' or 'find / -name aeheur.dll 2>/dev/null' to locate the file.
    Affected if The aeheur.dll file exists in any F-Secure or WithSecure installation directory.
  3. Determine if real-time scanning is enabled
    Check the antivirus configuration for real-time or on-access scanning status. On Windows, check the F-Secure GUI settings or registry keys under 'HKLM\Software\F-Secure'. On Linux, run 'fsav --version' or check 'f-secure' daemon status via 'systemctl status fsamd' or similar service.
    Affected if Real-time scanning or on-access scanning is currently enabled and active.
  4. Verify the scanning engine handles aeheur.dll
    Trigger a manual scan of the aeheur.dll file itself using the installed F-Secure/WithSecure product. On Windows, right-click the DLL file and select 'Scan with F-Secure'. On Linux, use 'fsav /path/to/aeheur.dll'. Monitor if the scanning engine crashes or becomes unresponsive.
    Affected if Scanning the aeheur.dll file causes the antivirus scanning engine to crash, hang, or become unresponsive.

If any of the affected F-Secure/WithSecure products are installed with the aeheur.dll component present and real-time scanning enabled, the environment is vulnerable to CVE-2022-28876 denial-of-service when that specific DLL file is scanned.

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 from Fsecure/WithSecure to update the scanning engine to a version that properly handles the aeheur.dll component. As a temporary workaround, consider excluding aeheur.dll from real-time scanning until the patch is applied, though this may reduce heuristic detection capabilities.

Fix this in Atlant Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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