dbcve.org
AtlantApplication · F Secure

CVE-2021-33603

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 AVPACK 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

The AVPACK module component in F-Secure Atlant crashes when scanning specially crafted fuzzed files, causing a denial of service of the Anti-Virus engine. The vulnerability can be triggered remotely by an attacker via a malicious file.

MitigationApply the vendor patch from F-Secure when available. As a defensive measure, consider restricting or disabling real-time scanning of untrusted files until the patch is applied.

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
    Run 'rpm -qa | grep -i fsecure' on Linux or check installed programs on Windows for any of these products: F-Secure Atlant, F-Secure Cloud Protection for Salesforce, F-Secure Elements for Microsoft 365, F-Secure Internet Gatekeeper, F-Secure Linux Security, F-Secure Elements Endpoint Detection and Response, or F-Secure Elements Endpoint Protection
    Affected if Any of the affected products listed in the CVE are installed on the system
  2. Check installed F-Secure version
    Use the product-specific command or GUI to determine the version of the installed F-Secure product. On Linux, check /opt/f-secure/fsma or use 'fsma --version'. On Windows, check Add/Remove Programs or the product's About section
    Affected if The product version matches any of the affected products listed (all versions are affected according to the CVE)
  3. Verify AVPACK module is present
    Check for the presence of the AVPACK module in the F-Secure installation directory. Common paths include /opt/f-secure/ or C:\Program Files\F-Secure\. Look for files named avpack, libavpack, or similar
    Affected if The AVPACK module exists in the F-Secure installation directory, indicating the vulnerable component is present
  4. Confirm real-time or on-access scanning is enabled
    Check the F-Secure product settings or run 'fsaua --status' (Linux) or check the client UI to see if real-time scanning, on-access scanning, or resident protection is active
    Affected if Real-time or on-access scanning is enabled, which allows the vulnerability to be triggered when a malicious file is scanned

If any of the affected F-Secure products are installed with the AVPACK module present and real-time scanning enabled, the environment is vulnerable to CVE-2021-33603 and could experience a denial of service when scanning specially crafted files.

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 patch from F-Secure when available. As a defensive measure, consider restricting or disabling real-time scanning of untrusted files until the patch is applied.

Fix this in Atlant Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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