CVE-2021-22961
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 code injection vulnerability exists within the firewall software of GlassWire v2.1.167 that could lead to arbitrary code execution from a file in the user path on first execution.
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 confidenceGlassWire v2.1.167 firewall software contains a code injection vulnerability that allows arbitrary code execution via a malicious file placed in the user path during the application's first execution. The vulnerability likely stems from insecure dynamic library or executable loading that does not properly validate or restrict files loaded from user-writable directories.
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= 2.1.167CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 GlassWire installationCheck if GlassWire software is installed on the system by searching for GlassWire in installed programs (Windows: Control Panel > Programs and Features, or check C:\Program Files\GlassWire or C:\Program Files (x86)\GlassWire directories)Affected if GlassWire is found installed on the system
-
Identify installed GlassWire versionLocate the installed GlassWire executable (typically in Program Files\GlassWire or Program Files (x86)\GlassWire), right-click the executable, select Properties, and check the Details tab for the File Version or Product VersionAffected if The installed version is exactly 2.1.167
-
Confirm vulnerability applicabilitySince the vulnerability requires a malicious file to be placed in a user-writable path during the application's first execution, review any recently created or modified files in user directories (especially Downloads, Documents, or user profile folder) that may have been present during GlassWire's initial runAffected if GlassWire version 2.1.167 is installed AND there is potential for untrusted files to exist in user-writable paths that GlassWire could load during initialization
-
Check for suspicious DLL or executable filesInspect the GlassWire installation directory and user-writable directories for unexpected DLL files or executables that may have been placed there, particularly in locations where GlassWire loads libraries from (check the application directory and user profile paths)Affected if Unexpected DLL or executable files are found in locations GlassWire loads libraries from on a version 2.1.167 installation
A user is affected if GlassWire version 2.1.167 is installed and the system had untrusted files in user-writable paths during the application's first execution, allowing insecure library loading.
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 dataUpgrade to a patched version of GlassWire beyond v2.1.167 that addresses the code injection vulnerability. As an interim measure, ensure no untrusted files exist in user-writable paths that GlassWire might load during initialization.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22961 — 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-2021-22961 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