LiveActive security incident?Get immediate response
CVE Record

CVE-2019-20079: The autocmd feature in window.c in Vim before 8.1.2136 accesses freed memory.

The autocmd feature in window.c in Vim before 8.1.2136 accesses freed memory.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Vim before 8.1.2136 has a memory-safety flaw in its autocmd handling. In practical terms, an editor used on servers or developer workstations could behave unsafely when vulnerable code paths are triggered. The bundle does not provide CVSS, confirmed active exploitation, or detailed business impact, so urgency should be driven by asset exposure and upgrade feasibility.

Executive priority

Handle as a routine-to-expedited patching item, not an emergency based on the provided evidence. Prioritize environments where Vim is used by administrators, developers, or automation on sensitive systems, and close inventory gaps because the affected-products metadata is incomplete.

Technical view

CVE-2019-20079 is a use-after-free condition in Vim's autocmd feature within window.c, fixed around Vim 8.1.2136. The public references include the upstream commit, version comparison, Packet Storm entry, and Ubuntu advisory USN-4309-1. The bundle does not include CWE, CVSS, or detailed exploit preconditions.

Likely exposure

Exposure is most likely on systems running Vim versions before 8.1.2136, including developer workstations, admin jump hosts, and Unix/Linux servers with vulnerable distro packages. The provided affected-products metadata is incomplete, so confirm through package inventory rather than assuming all Vim installations are affected.

Exploitation context

The source bundle lists a Packet Storm reference, indicating public technical material exists. It does not show CISA KEV inclusion, CVSS scoring, or confirmed active exploitation. Treat exploitability as plausible for vulnerable versions, but do not claim in-the-wild exploitation from these sources.

Researcher notes

Focus validation on the upstream fix commit and the 8.1.2135-to-8.1.2136 diff for window.c autocmd lifetime handling. Avoid relying on the sparse CVE affected-product fields. Packet Storm suggests public technical details, but the bundle does not prove active exploitation.

Mitigation direction

  • Upgrade Vim to 8.1.2136 or a vendor-patched later package.
  • Apply Ubuntu guidance from USN-4309-1 where Ubuntu packages are used.
  • Check other OS vendor advisories for backported Vim fixes.
  • Reduce use of vulnerable Vim on systems handling untrusted files.
  • Prioritize shared servers and administrator workstations for remediation.

Validation and detection

  • Inventory installed Vim package versions across servers and workstations.
  • Confirm whether vendor packages include the upstream 8.1.2136 fix or a backport.
  • Review Ubuntu systems against USN-4309-1 package status.
  • Check configuration management for pinned or locally built Vim versions.
  • Document exceptions where Vim cannot be upgraded immediately.
Prepared
Confidence
medium
Sources
6

Public sources used

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-20079 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
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
5Source links

CVSS and timeline data

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

Source materials

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.