dbcve.org
AtlantApplication · F Secure

CVE-2021-40832

MEDIUM · 6.5 CVSS v3.1 Published 2021-10-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 whereby the AVRDL unpacking module component used in certain F-Secure products can crash while scanning a fuzzed files. The exploit can be triggered remotely by an attacker. A successful attack will result in Denial-of-Service (DoS) of the Anti-Virus engine.

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 AVRDL unpacking module of F-Secure Atlant (used in certain F-Secure AV products). When scanning a specially crafted fuzzed file, the unpacking module crashes, causing the entire Anti-Virus engine to become unavailable. The vulnerability can be triggered remotely via file scanning.

MitigationApply the official F-Secure security update/patch when released. Consider implementing additional file-type filtering at network boundaries to reduce exposure to malformed files pending patch deployment.

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 For Microsoft 365Application
Affected:all versions
Internet GatekeeperApplication
Affected:all versions
Linux SecurityApplication
Affected:all versions
Elements Endpoint Detection And ResponseApplication
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
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 products
    List installed software on the system and look for any of these F-Secure products: Atlant, Cloud Protection for Salesforce, Elements for Microsoft 365, Internet Gatekeeper, Linux Security, Elements Endpoint Detection and Response, or Elements Endpoint Protection. On Linux, check /opt/f-secure or run 'rpm -qa | grep -i f-secure' or 'dpkg -l | grep -i f-secure'. On Windows, check Programs and Features or use 'wmic product get name,version'.
    Affected if Any of the listed F-Secure products are installed on the system
  2. Verify the Atlant component is present
    Locate the f-secure Atlant installation directory. On Linux, common paths include /opt/f-secure/atlant or /opt/f-secure/fsav. On Windows, check C:\Program Files\F-Secure\Atlant. Look for the avrdl module or unpacking component.
    Affected if The F-Secure Atlant component directory and its avrdl module exist on the system
  3. Confirm file scanning is enabled
    Check if real-time or on-demand file scanning is active. For command-line tools, run the AV scanner with version info (e.g., 'fsav --version' or the equivalent for your product). For GUI installations, verify scanning profiles are not disabled. Check configuration files for scanning-enabled status.
    Affected if File scanning or real-time protection is turned ON in the F-Secure product configuration
  4. Check for recent security updates
    Query the F-Secure product for its update status and installed patch level. On Linux, check /var/opt/f-secure/ for update logs or run 'fsupctl -v'. Review the F-Secure knowledge base or product about dialog for the installed version number and compare against any post-CVE release notes.
    Affected if The installed F-Secure Atlant version predates the CVE-2021-40832 patch release date and has not received security updates

If any F-Secure product from the affected list is installed with file scanning enabled and the Atlant component is present without the CVE-2021-40832 security patch, the environment is vulnerable to the denial-of-service condition.

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 official F-Secure security update/patch when released. Consider implementing additional file-type filtering at network boundaries to reduce exposure to malformed files pending patch deployment.

Fix this in Atlant Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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