CVE-2022-28880
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 vulnerability was discovered in the F-Secure Atlant and in certain WithSecure products while scanning fuzzed PE32-bit files it is possible that 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 · moderate confidenceA Denial-of-Service vulnerability exists in F-Secure Atlant and certain WithSecure products where scanning fuzzed PE32-bit (Portable Executable 32-bit) files can crash the scanning engine. The vulnerability is remotely exploitable by an attacker sending specially crafted malicious files for scanning.
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 versionsall versionsall versionsall 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
- 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.
-
Identify installed F-Secure/WithSecure productsRun 'rpm -qa | grep -i f-secure' or 'dpkg -l | grep -i f-secure' on Linux; on Windows check Programs and Features or run 'wmic product get name,version'Affected if Any of these products are found: Elements Endpoint Detection And Response, Elements Endpoint Protection, Atlant, Cloud Protection For Salesforce, Elements Collaboration Protection, Internet Gatekeeper, Linux Security, or Linux Security 64
-
Check if real-time or on-demand scanning is enabledFor Linux products, check the scanning daemon status via 'systemctl status f-secure' or similar; for Windows, check the security product settings for real-time scanning statusAffected if Real-time scanning or on-demand file scanning is turned on and active
-
Verify PE32 file scanning capability is activeCheck the product configuration for file type scanning settings - look for PE, executable, or 'all files' scanning options enabledAffected if PE32 file scanning is not explicitly disabled in the product settings
-
Confirm scanning engine handles executable filesTest by scanning a benign PE32 file using the product's command-line scanner if available (e.g., 'fsav --scan <filename>'), or check logs for recent PE32 file scansAffected if The scanning engine processes PE32 files as part of its normal operation
The environment is affected if any of the listed F-Secure/WithSecure products are installed with scanning functionality enabled, as the vulnerability triggers when the engine processes malicious PE32 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 dataOrganizations using affected F-Secure/WithSecure products should apply vendor security updates or patches as soon as available. As an immediate workaround, consider restricting or disabling automatic scanning of untrusted PE32 files until the patch is applied.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28880 — 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-28880 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