CVE-2022-28964
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 · uneditedAn arbitrary file write vulnerability in Avast Premium Security before v21.11.2500 (build 21.11.6809.528) allows attackers to cause a Denial of Service (DoS) via a crafted DLL file.
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 confidenceAvast Premium Security before version 21.11.2500 contains an arbitrary file write vulnerability that can be triggered by a crafted DLL file, leading to denial of service. The vulnerability exists in the security product's handling of DLL files, allowing attackers to write arbitrary files to the system.
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 data< 21.11.2500CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Avast Premium Security is installedCheck for Avast Premium Security in Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look in Program Files for Avast Software folderAffected if Avast Premium Security is not found on the system, the vulnerability does not apply
-
Determine installed version of Avast Premium SecurityOpen Programs and Features in Control Panel, find Avast Premium Security, and note the version column, or right-click the Avast icon and select 'About Avast'Affected if The displayed version number is less than 21.11.2500 (for example, 21.10.x or earlier)
-
Confirm DLL handling component is activeCheck if Avast's Real-Time Shields or File System Shield is enabled - open Avast interface, go to Protection, and verify at least one shield is activeAffected if The shields are disabled, the specific attack vector may not be reachable, though the vulnerable code still exists in the product
-
Review Avast logs for suspicious DLL activityOpen Avast UI, go to Settings > General > Logs, or check %ProgramData%\Avast\Logs for entries containing 'dll' and 'write' or 'create' around the time of any suspected incidentsAffected if Logs show attempts to write DLL files to unusual locations or denied operations related to DLL handling
A system is affected if Avast Premium Security is installed with a version lower than 21.11.2500 and the security product's DLL handling functionality is active.
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.
dbcve · scoped21.11.2500
Upgrade Avast Premium Security to version 21.11.2500 (build 21.11.6809.528) or later to remediate this vulnerability.
Avast Premium Security v21.11.2500 (build 21.11.6809.528) or later
- Upgrade Avast Premium Security to version 21.11.2500 (build 21.11.6809.528) or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28964 — 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-28964 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