LiveActive security incident?Get immediate response
CVE Record

CVE-2021-3872: Heap-based Buffer Overflow in vim/vim

vim is vulnerable to Heap-based Buffer Overflow

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-3872 is a heap-based buffer overflow in Vim. The public record rates it high severity because exploitation could affect confidentiality, integrity, and availability, but it requires local access and user interaction. The source bundle does not provide affected version ranges.

Executive priority

Treat this as a high-priority hygiene fix for managed endpoints and server images, not as an internet-exposed emergency. The main business concern is unpatched tooling on systems where staff or automation may process untrusted files.

Technical view

The CVE describes CWE-122 in vim/vim with CVSS 3.0 score 7.8. Vector AV:L/AC:L/PR:N/UI:R means exploitation is local, low complexity, requires no privileges, and needs user interaction. Upstream commit 826bfe4bbd7594188e3d74d2539d9707b1c6a14b is cited as the fix reference.

Likely exposure

Exposure is most likely on developer workstations, administrator systems, servers, containers, and base images that include Vim. Risk depends on whether installed packages predate vendor backports or the upstream fix. Affected versions are unspecified in the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cite active exploitation. Based on CVSS, a realistic scenario requires a local interaction with Vim and could cause high impact if successfully triggered. No weaponized details are provided here.

Researcher notes

Evidence is sufficient for classification, impact, and remediation direction, but incomplete for exact affected version ranges and trigger conditions. Use vendor advisories and package changelogs for validation. Do not assume a package is vulnerable solely from the upstream version string if the vendor backported the fix.

Mitigation direction

  • Update Vim through the operating system or package vendor security channel.
  • If building from upstream, ensure the cited fix commit is included.
  • Prioritize systems where users open untrusted files in Vim.
  • Check Fedora, Debian LTS, and Gentoo advisories for distribution-specific fixed packages.
  • Where immediate updating is unavailable, reduce use of Vim on untrusted content.

Validation and detection

  • Inventory installed Vim packages across endpoints, servers, containers, and build images.
  • Compare installed package builds against relevant vendor security advisories.
  • For source builds, verify the cited upstream commit is present.
  • Confirm vulnerability scanner findings against package backport metadata.
  • Document any unsupported systems requiring compensating controls or replacement.
Prepared
Confidence
medium
Sources
8

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.

cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-3872 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
High
CVSS
7.8 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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.

1CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.0HighCVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.8High
CVSS 3.0 vector shape for CVE-2021-3872Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
vimvim/vimunspecifiedListed
Weakness

CWE details

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

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.