CVE-2022-28882
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 & WithSecure products whereby the aegen.dll will go into an infinite loop when unpacking PE files. This eventually 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 F-Secure/WithSecure's aegen.dll component used for unpacking PE (Portable Executable) files during antivirus scanning. When processing specially crafted PE files, the library enters an infinite loop that causes the scanning engine to crash, enabling remote attackers to trigger the DoS condition.
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 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 system inventory commands (e.g., 'dpkg -l', 'rpm -qa', or check Programs and Features on Windows) to list installed security products. Look for: 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-Secure Linux Security 64.Affected if Any of the listed F-Secure/WithSecure products are installed on the system.
-
Locate the aegen.dll componentSearch for aegen.dll on the system. Common paths include installation directories such as '/opt/f-secure/' on Linux or 'C:\Program Files\F-Secure\' on Windows. Use 'find / -name aegen.dll 2>/dev/null' on Linux or check the product installation directory.Affected if The aegen.dll file exists on the system, indicating the vulnerable PE unpacking component is present.
-
Verify PE file scanning is enabledCheck the F-Secure product configuration settings or policy files for scanning of executable (PE) files. On Linux, inspect /opt/f-secure/*/configuration files or run 'psax | grep' for scanning daemon processes. Look for settings related to 'PE scanning', 'on-demand scanning', or 'real-time scanning'.Affected if PE file scanning or on-access scanning is enabled, which activates the vulnerable aegen.dll code path.
-
Check for recent scanning activity logsReview F-Secure scanning logs (typically in /var/log/f-secure/ or within the product's log directory) for entries related to PE file unpacking or aegen. Look for patterns indicating recent PE file scans.Affected if The product has been used to scan PE files, demonstrating the vulnerable code path could be triggered.
If any of the affected F-Secure/WithSecure products are installed with the aegen.dll component present and PE scanning enabled, the environment is potentially affected by this DoS vulnerability.
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 vendor-supplied security patches for F-Secure/WithSecure products as soon as they become available. Consider implementing file-type scanning restrictions or leveraging alternative scanning methods for untrusted PE files as a temporary workaround until the patch is applied.
- Consultation2.0 h
- Implementation1.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28882 — 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-28882 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