dbcve.org
AntivirusApplication · Avast

CVE-2024-9482

MEDIUM · 5.5 CVSS v3.1 Published 2024-10-04
Fix available
A fix is available. Upgrade to 24092400 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
An out-of-bounds write in the engine module in AVG/Avast Antivirus signature <24092400 released on 24/Sep/2024 on MacOS allows a malformed Mach-O file to crash the application during file processing.

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 confidence

An out-of-bounds write vulnerability exists in the engine module of AVG/Avast Antivirus for MacOS when processing malformed Mach-O files. The vulnerability affects antivirus signature versions prior to 24092400 (released September 24, 2024), allowing specially crafted Mach-O files to trigger memory corruption leading to application crashes during file scanning operations.

MitigationUpdate AVG/Avast Antivirus to signature version 24092400 or later, or apply the latest vendor patch to remediate this vulnerability. Organizations should also consider restricting processing of untrusted Mach-O files until the update is applied.

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
AntivirusApplication
Affected:< 24092400
AntivirusApplication
Affected:< 24092400

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify AVG or Avast Antivirus is installed on macOS
    Check /Applications folder for 'Avast Antivirus.app' or 'AVG Antivirus.app', or use command: ls /Applications | grep -i 'avast\|avg'
    Affected if Either application is present on the system
  2. Locate the application version file
    Right-click the installed app, select 'Get Info', or use terminal: defaults read /Applications/Avast\ Antivirus.app/Contents/Info CFBundleVersion 2>/dev/null || defaults read /Applications/AVG\ Antivirus.app/Contents/Info CFBundleVersion 2>/dev/null
    Affected if Unable to retrieve version indicates product may not be properly installed
  3. Check the antivirus signature/definition version
    Open the application, navigate to Settings > About, or check the virus database version displayed in the main interface. On command line, check: defaults read /Applications/Avast\ Antivirus.app/Contents/Info AVGEngineVersion 2>/dev/null || defaults read /Applications/AVG\ Antivirus.app/Contents/Info AVGEngineVersion 2>/dev/null
    Affected if Signature version displayed is below 24092400
  4. Confirm vulnerability applicability
    Review the signature version: the engine processes Mach-O files during scheduled or on-demand scans. The vulnerability is present in any version prior to 24092400 regardless of scan configuration, but active scanning capability is required for exploitation.
    Affected if Product is installed AND signature version is less than 24092400

A user is affected if AVG or Avast Antivirus for macOS is installed with a signature or engine version below 24092400.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 24092400 or later
Fixed in 24092400
Interim mitigation

Update AVG/Avast Antivirus to signature version 24092400 or later, or apply the latest vendor patch to remediate this vulnerability. Organizations should also consider restricting processing of untrusted Mach-O files until the update is applied.

Recommended fix High confidence

Antivirus signature version 24092400 or later (released September 2024)

  1. 1. Open the AVG or Avast Antivirus application on the MacOS system
  2. 2. Navigate to the application settings or preferences
  3. 3. Check the current version and signature database version (ensure it is below 24092400)
  4. 4. Look for an update option within the application (usually in Settings > Update or Help > Check for Updates)
  5. 5. Click to check for and install updates
  6. 6. Verify the signature version has been updated to 24092400 or later
  7. 7. Restart the antivirus application if prompted

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Antivirus Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9482 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9482 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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