Application crash via malformed EML engine write
Published Oct 4, 2024 · Updated Oct 7, 2024
Out-of-bounds write in AVG/Avast Antivirus definitions before 24092400 allows local users to crash the macOS application with a malformed EML file. The engine module writes outside its intended buffer while processing the malformed EML. Triggering requires local file processing; the published impact is an application crash without confidentiality or integrity loss.
Summary
What happened
Out-of-bounds write in AVG/Avast Antivirus definitions before 24092400 allows local users to crash the macOS application with a malformed EML file. The engine module writes outside its intended buffer while processing the malformed EML. Triggering requires local file processing; the published impact is an application crash without confidentiality or integrity loss.
The record
- CVE
- CVE-2024-9481
- Published
- Oct 4, 2024
- Updated
- Oct 7, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 4, 2024CVE publishedPublication date reported by the CVE source.
- Oct 7, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo