CVE-2024-6510
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 · uneditedLocal Privilege Escalation in AVG Internet Security v24 on Windows allows a local unprivileged user to escalate privileges to SYSTEM via COM-Hijacking.
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 confidenceLocal privilege escalation vulnerability in AVG Internet Security v24 on Windows where an unprivileged local user can escalate to SYSTEM privileges through COM-Hijacking. The attacker manipulates COM object registrations to redirect component activation to malicious code running in an elevated context.
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< 24.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Check if AVG Internet Security is installedOpen Programs and Features (appwiz.cpl) or check registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\AvgInternetSecurity for the DisplayVersion valueAffected if AVG Internet Security is present on the system
-
Determine installed AVG Internet Security versionIf found in Programs and Features, note the version number shown; alternatively, query registry key HKLM\SOFTWARE\Avg\Settings\InstallInfo for value 'AppVersion' or check AVG's program directory for a version fileAffected if Version is below 24.1 (e.g., 23.x, 24.0.x)
-
Verify the vulnerable AVG component is presentCheck if AVG Internet Security services or components are installed: look for AVG services (e.g., avgStm, avgAv, avgDiag) in services.msc or check for AVG installation directory at C:\Program Files\AVG\Antivirus or C:\Program Files (x86)\AVG\AntivirusAffected if AVG Internet Security is installed and running as a service or background component
-
Inspect COM object registrations for AVGOpen registry editor and examine COM CLSID keys under HKLM\SOFTWARE\Classes\CLSID and HKCR\CLSID, specifically looking for entries containing 'AVG' in the InprocServer32 path that point to non-standard DLL locations, or use PowerShell: Get-ItemProperty -Path 'HKLM:\SOFTWARE\Classes\CLSID\*' -ErrorAction SilentlyContinue | Where-Object {$_.Name -like '*AVG*'}Affected if COM objects related to AVG point to unexpected DLL paths or show recent modification dates indicating tampering
-
Check for unauthorized COM hijacking indicatorsCompare current COM registrations against known-good baseline if available; otherwise, look for COM objects with NULL or empty server paths, or paths in user-writable directories (e.g., %TEMP%, %APPDATA%, C:\Users\*) under HKCU\SOFTWARE\Classes\CLSIDAffected if Any AVG-related COM objects have been modified to load code from user-accessible locations
User is affected if AVG Internet Security version is below 24.1 AND the AVG component is installed and running, with evidence of COM object manipulation enabling privilege escalation
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 · scoped24.1
Apply vendor patch when released by AVG. In the interim, restrict local user permissions, monitor for unauthorized COM object modifications, and consider disabling or removing the vulnerable AVG component if operationally feasible.
AVG Internet Security 24.1 or later
- 1. Open AVG Internet Security application
- 2. Navigate to Menu > Settings > About > Update now
- 3. Alternatively, download the latest version from official AVG website (www.avg.com)
- 4. Run the installer and complete the upgrade to version 24.1 or later
- 5. Restart the computer to ensure all components are updated
- 6. Verify the installed version by checking Menu > Settings > About to confirm version 24.1 or higher is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6510 — 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-2024-6510 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