CVE-2023-1587
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 · uneditedAvast and AVG Antivirus for Windows were susceptible to a NULL pointer dereference issue via RPC-interface. The issue was fixed with Avast and AVG Antivirus version 22.11
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 and AVG Antivirus for Windows contained a NULL pointer dereference vulnerability in their RPC interface that could cause the application to crash or become unstable. NULL pointer dereferences occur when the software attempts to access memory at a null address, typically leading to an access violation or denial of service 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 data>= 22.5, < 22.11>= 22.5, < 22.11CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Confirm Avast or AVG Antivirus is installedOpen Windows Settings > Apps & Features (or use Control Panel > Programs and Features) and look for 'Avast Antivirus' or 'AVG AntiVirus' in the installed programs list. Alternatively, right-click the system tray icon to identify the product.Affected if Either Avast Antivirus or AVG AntiVirus is present on the Windows system
-
Identify the installed antivirus versionRight-click the Avast or AVG icon in the system tray, select 'About', or open the main program interface and navigate to Menu > Settings > About. The version number is displayed in the About window.Affected if The displayed version falls within the range 22.5.0 through 22.10.x (any version >= 22.5 but < 22.11)
-
Verify the RPC interface component existsCheck that the antivirus real-time protection is enabled and the core service is running. Open Windows Services (services.msc) and verify the Avast Antivirus or AVG Antivirus service is in a 'Running' state.Affected if The antivirus service is running with a vulnerable version, as the RPC interface is a built-in component of the affected versions
If Avast Antivirus or AVG AntiVirus version 22.5 through 22.10.x is installed and running on Windows, the system is affected by this CVE.
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 · scoped22.11
Upgrade to Avast or AVG Antivirus version 22.11 or later. For enterprise deployments, verify current version inventory and deploy the update through standard patch management processes.
Avast Antivirus version 22.11 or later; AVG Antivirus version 22.11 or later
- 1. Open your Avast or AVG Antivirus application
- 2. Navigate to Menu > Settings
- 3. Go to the General section and click on Update
- 4. Click on Check for updates to download and install version 22.11 or later
- 5. Restart the computer if prompted
- 6. Verify the installed version is 22.11 or higher by checking Menu > Settings > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1587 — 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-2023-1587 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