LiveActive security incident?Get immediate response
CVE Record

CVE-2017-6349: An integer overflow at a u_read_undo memory allocation site would occur for vim before patch 8.0.0377, if i...

An integer overflow at a u_read_undo memory allocation site would occur for vim before patch 8.0.0377, if it does not properly validate values for tree length when reading a corrupted undo file, which may lead to resultant buffer overflows.

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

Security readout for executives and security teams

Plain-English summary

CVE-2017-6349 is a Vim file-parsing memory corruption issue. A malformed undo file can trigger an integer overflow while Vim allocates memory, potentially leading to buffer overflows. Business risk is mainly on systems where users open or process untrusted files with older Vim versions.

Executive priority

Prioritize normal vulnerability management rather than emergency response unless older Vim is widely deployed on sensitive systems. Patch developer and administrator environments first because they commonly handle external files and have privileged access.

Technical view

Vim before patch 8.0.0377 did not properly validate tree-length values while reading corrupted undo files in u_read_undo. The bad length can overflow allocation sizing and create downstream buffer overflow conditions. The provided sources do not include CVSS, CWE, or confirmed exploit details.

Likely exposure

Exposure is likely limited to systems running Vim before patch 8.0.0377, especially developer workstations, admin servers, jump hosts, and automated workflows that may open untrusted files or associated undo data.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. The attack appears user-assisted or file-driven: Vim must read a corrupted undo file. Impact depends on platform hardening and how Vim is used.

Researcher notes

Key evidence is concise: the CVE description names the integer overflow and patch boundary, and the upstream commit is the primary fix reference. The bundle lacks CVSS, CWE mapping, proof-of-concept status, and detailed exploitability analysis, so confidence is bounded.

Mitigation direction

  • Upgrade Vim using vendor-supported packages or a build including patch 8.0.0377 or later.
  • Review Gentoo, Ubuntu, or your OS vendor advisory for the fixed package version.
  • Avoid opening untrusted files and associated undo data with vulnerable Vim builds.
  • Where patching is delayed, reduce use of persistent undo data from untrusted locations.

Validation and detection

  • Inventory Vim versions on workstations, servers, containers, and administrative images.
  • Confirm installed Vim includes patch 8.0.0377 or a vendor backport.
  • Check configuration and workflows for persistent undo files in shared or untrusted directories.
  • Verify vendor package changelogs reference CVE-2017-6349 or the upstream Vim fix.
Prepared
Confidence
medium
Sources
5

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-2017-6349 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.