CVE-2021-33598
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 · uneditedA Denial-of-Service (DoS) vulnerability was discovered in all versions of F-Secure Atlant whereby the SAVAPI component used in certain F-Secure products can crash while scanning 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 confidenceA Denial-of-Service vulnerability exists in F-Secure Atlant's SAVAPI component where the anti-virus engine crashes when scanning fuzzed/malformed files. The crash occurs during the file scanning process and can be triggered remotely, resulting in complete unavailability of the Anti-Virus engine.
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 dataall versionsall versionsall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if F-Secure SAVAPI or Atlant is installedCheck for F-Secure SAVAPI or Atlant processes running on the system using commands like 'ps aux | grep -i savapi' or 'ps aux | grep -i atlant', or check installed packages using the system package managerAffected if F-Secure SAVAPI or Atlant processes or packages are found on the system
-
Confirm the AV scanning component is activeCheck if the SAVAPI scanning service is running and enabled using commands like 'systemctl status savapi' or by reviewing the process list for active anti-virus scanning daemonsAffected if The SAVAPI scanning service or daemon is running and active
-
Determine if real-time or on-demand scanning is enabledReview the F-Secure configuration files or settings to check if real-time file scanning (e.g., on-access scanning) or on-demand scanning is turned on. Check configuration files in /etc/f-secure/ or use the f-secure command-line tools if availableAffected if Real-time scanning or on-demand file scanning is enabled and active
-
Verify product installation typeUse system package management tools (dpkg, rpm, yum) to list installed F-Secure packages, or check for F-Secure installation directories and binariesAffected if Any of the affected products (F-Secure Atlant, F-Secure Linux Security, or F-Secure Elements Endpoint Protection) are installed
If F-Secure SAVAPI/Atlant is installed and the scanning engine is enabled, the system is vulnerable to CVE-2021-33598 DoS via malformed file scanning.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-supplied patch or update to a fixed version of F-Secure Atlant/SAVAPI. Consider implementing file-type restrictions or scanning timeouts as a defense-in-depth measure until the patch can be applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33598 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-33598 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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