CVE-2019-11230: n/a vulnerability

CVE-2019-11230: In Avast Antivirus before 19.4, a local administrator can trick the product into renaming arbitrary files b...

In Avast Antivirus before 19.4, a local administrator can trick the product into renaming arbitrary files by replacing the Logs\Update.log file with a symlink. The next time the product attempts to write to the log file, the target of the symlink is renamed. This defect can be exploited to rename a critical product file (e.g., AvastSvc.exe), causing the product to fail to start on the next system restart.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 4, 2024, 22:48 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2019-11230 lets a local administrator disrupt Avast Antivirus before version 19.4 by abusing how the product handled an update log file. The practical business risk is security-control outage: Avast may fail to start after reboot if a critical product file is renamed. Exposure appears limited to systems running Avast Antivirus before 19.4 where an attacker already has local administrator privileges. The bundle does not provide CPEs, edition details, operating-system scope, or complete affected-product metadata. Treat as a moderate-priority endpoint hardening issue. It does not appear remotely exploitable from the provided sources, but it can disable antivirus on already-compromised or administrator-accessed systems, reducing detection and response capability. Mitigation focus: Upgrade Avast Antivirus to version 19.4 or later where applicable.; Check Avast vendor guidance for affected editions and supported remediation paths.; Reduce unnecessary local administrator rights on endpoints..

Prepared: Jun 6, 2026, 20:22 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-11230 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jul 18, 2019, 16:50 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.