LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2304: Stack-based Buffer Overflow in vim/vim

Stack-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-2304 is a high-severity stack-based buffer overflow in Vim before 9.0. If triggered, the CVSS rating indicates possible loss of confidentiality, integrity, and availability. The source bundle does not show active exploitation or provide trigger details.

Executive priority

Treat this as a routine high-priority patching item, especially for developer and administrator systems. It is serious because impact is rated high, but the provided evidence does not support emergency treatment for active exploitation.

Technical view

The CVE describes CWE-121 in vim/vim prior to 9.0 with CVSS 7.8. The vector is local, low complexity, no privileges required, and user interaction required. The bundle links an upstream Vim commit and multiple Linux distribution advisories.

Likely exposure

Exposure is likely wherever vulnerable Vim versions before 9.0, or distribution packages lacking the relevant backport, are installed on endpoints, servers, build images, or administrative workstations.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. CVSS indicates local attack vector and required user interaction, so exploitation is not described as remotely automatic.

Researcher notes

Evidence is limited to the CVE metadata, upstream fix reference, Huntr report, and distribution advisories. The bundle does not include detailed vulnerable code path, proof-of-concept status, or exploit telemetry, so validation should focus on version and vendor backport status.

Mitigation direction

  • Upgrade Vim to version 9.0 or later where feasible.
  • Apply vendor-patched Vim packages from the relevant Linux distribution.
  • Check whether packaged builds include the upstream fix commit or equivalent backport.
  • Prioritize systems where administrators or developers process untrusted files.
  • Follow vendor advisories if exact package status is unclear.

Validation and detection

  • Inventory installed Vim versions across endpoints, servers, containers, and build images.
  • Verify vulnerable assets are not running Vim versions prior to 9.0 without backports.
  • Review package changelogs for the referenced upstream fix or distribution security update.
  • Confirm Fedora, Gentoo, Debian, or other vendor advisories match deployed package versions.
  • Document remaining exceptions and compensating controls for vulnerable installations.
Prepared
Confidence
high
Sources
10

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.

cwe · low confidence lookup

CWE-121: 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-2022-2304 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
9Source 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-2022-2304Attack 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-121

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