CVE-2022-28871
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 F-Secure Atlant whereby the fsicapd component used in certain F-Secure products while scanning larger packages/fuzzed files consume too much memory eventually 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 confidenceA denial-of-service vulnerability exists in F-Secure's fsicapd component (the ICAP daemon used for content scanning). When scanning larger packages or fuzzed files, the component consumes excessive memory due to improper resource handling, eventually causing the scanning engine to crash. The vulnerability can be triggered remotely by an attacker sending specially crafted large files.
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 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify fsicapd service statusCheck if the fsicapd (F-Secure ICAP Daemon) service is running on the system. On Linux: 'systemctl status fsicapd' or 'ps aux | grep fsicapd'. On Windows: Check Services console or run 'sc query fsicapd'.Affected if The fsicapd service is actively running and processing ICAP requests
-
Identify installed F-Secure Atlant versionCheck the installed version of F-Secure Atlant. On Linux: 'rpm -q f-secure-atlant' or 'dpkg -l | grep atlant'. On Windows: Check Add/Remove Programs or use 'f-secure-atlant --version' if available.Affected if Any version of F-Secure Atlant is installed (all versions are affected)
-
Confirm ICAP scanning is enabledInspect the fsicapd configuration file (typically at /etc/fsicapd/fsicapd.conf on Linux or in the F-Secure installation directory on Windows) and verify ICAP scanning is active. Look for 'EnableICAP=1' or similar directives.Affected if ICAP scanning functionality is enabled in the fsicapd configuration
-
Check ICAP service network exposureReview network configuration to determine if the ICAP service (default port 1344) is exposed to untrusted networks or the internet. Check firewall rules and fsicapd bind settings in the configuration file.Affected if The ICAP service is reachable from untrusted network segments, allowing remote attackers to send specially crafted files
A system is affected if F-Secure Atlant with fsicapd is installed, the ICAP scanning service is running and enabled, and the ICAP port is accessible to potential attackers who could send large malicious files.
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 the fixed version of F-Secure Atlant/affected products when available. Consider implementing ICAP request size limits or memory consumption thresholds as an interim compensating control.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28871 — 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-2022-28871 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