CVE-2022-4291
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 · uneditedThe aswjsflt.dll library from Avast Antivirus windows contained a potentially exploitable heap corruption vulnerability that could enable an attacker to bypass the sandbox of the application it was loaded into, if applicable. This issue was fixed in version 18.0.1478 of the Script Shield Component.
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 confidenceHeap corruption vulnerability in Avast Antivirus's aswjsflt.dll library (Script Shield Component). The flaw could allow an attacker to bypass application sandboxing when the DLL is loaded into a sandboxed application, potentially enabling privilege escalation and arbitrary code execution.
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<= 18.0.1473.0CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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 Antivirus installationCheck for Avast Antivirus installation via Programs and Features, or query the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Avast for the DisplayName valueAffected if Avast Antivirus is not installed on the system
-
Confirm Script Shield component is presentLocate the aswjsflt.dll file in the Avast installation directory (typically under Program Files\Avast), or check if Script Shield appears in Avast's component list via the UI or avastcmd /dump commandAffected if The aswjsflt.dll file (Script Shield) is not found in the Avast installation directory
-
Retrieve aswjsflt.dll versionRight-click the aswjsflt.dll file, select Properties, and view the File Version field, or use the command: powershell (Get-Item 'C:\Program Files\Avast\Software\aswjsflt.dll').VersionInfo.FileVersionAffected if Unable to retrieve version information for aswjsflt.dll
-
Compare version to affected rangeCompare the extracted version number to 18.0.1473.0. Versions 18.0.1473.0 and below are affected; version 18.0.1478 and later are patchedAffected if The installed version of aswjsflt.dll is 18.0.1473.0 or lower, indicating the system is vulnerable
The system is affected if Avast Antivirus with Script Shield is installed and the aswjsflt.dll component version is 18.0.1473.0 or lower.
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 · scopedUpgrade Avast Antivirus Script Shield Component to version 18.0.1478 or later to remediate the vulnerability.
Script Shield version 18.0.1478 or later
- Open Avast Antivirus or AVG Antivirus application
- Navigate to Settings or Menu > Update
- Locate the Script Shield component or general program update option
- Run the update to install the latest version of Script Shield
- Verify the installed version is 18.0.1478 or later via Settings > About > Components
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4291 — 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-4291 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