CVE-2022-28881
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 aerdl.dll component used in certain WithSecure products unpacker function crashes which leads to scanning engine crash. 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 the aerdl.dll unpacker component of F-Secure Atlant used in WithSecure products. When the unpacker function processes specially crafted input, it crashes, causing the entire scanning engine to crash. This can be triggered remotely by an attacker without authentication.
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 productsCheck installed programs list or running processes for F-Secure Elements, WithSecure, F-Secure Atlant, or related product names using Add/Remove Programs, system inventory tools, or process enumeration commands like tasklist or psAffected if Any of the following products are installed: F-Secure Elements Endpoint Detection And Response, F-Secure Elements Endpoint Protection, F-Secure Atlant, F-Secure Cloud Protection For Salesforce, F-Secure Elements Collaboration Protection, F-Secure Internet Gatekeeper, F-Secure Linux Security, or F-Se
-
Locate the aerdl.dll componentSearch for aerdl.dll file on the system using file search tools, command line utilities like 'find' or 'Get-ChildItem', or review the product installation directory for the F-Secure/WithSecure scanning engine componentsAffected if The aerdl.dll file is present in the F-Secure/WithSecure product installation directory
-
Confirm scanning or protection module is activeCheck if the F-Secure/WithSecure real-time scanning, file system protection, or content scanning features are enabled and running. This can be done via the product's status interface, service status, or process monitoring for scanning engine processesAffected if The real-time scanning, file system filter, or content scanning components are active and processing files
If any of the affected F-Secure/WithSecure products are installed and the scanning engine is active, the environment is vulnerable to CVE-2022-28881 as all versions of these products contain the vulnerable aerdl.dll unpacker component.
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 affected WithSecure/F-Secure products to address the aerdl.dll vulnerability. Until patched, consider network-level mitigations to limit exposure to maliciously crafted files.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28881 — 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-28881 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