Cyber Resilience

CVE-2024-41965

Memory Safety in Vim ≤ 9.1.0648

Memory Safety
Published
01 August 2024
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 4.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
EPSS Score 0.0029 21th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2024-41965 is a medium-severity Use After Free (CWE-416) vulnerability in Vim Vim. Its CVSS base score is 4.2 (Medium).

Operationally, ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Vim is an open source command line text editor. double-free in dialog_changed() in Vim < v9.1.0648. When abandoning a buffer, Vim may ask the user what to do with the modified buffer. If the user wants the changed buffer to…

more

be saved, Vim may create a new Untitled file, if the buffer did not have a name yet. However, when setting the buffer name to Unnamed, Vim will falsely free a pointer twice, leading to a double-free and possibly later to a heap-use-after-free, which can lead to a crash. The issue has been fixed as of Vim patch v9.1.0648.

CWE(s)
CWE-416CWE-415

Related Threats

CVEs Like This One

CVE-2024-41957Same product: Vim Vim
CVE-2023-48706Same product: Vim Vim
CVE-2025-55157Same product: Vim Vim
CVE-2025-55158Same product: Vim Vim
CVE-2023-46246Same product: Vim Vim
CVE-2023-5535Same product: Vim Vim
CVE-2025-26603Same product: Vim Vim
CVE-2023-48231Same product: Vim Vim
CVE-2024-47814Same product: Vim Vim
CVE-2023-4750Same product: Vim Vim

Affected Assets

vim
vim
≤ 9.1.0648

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 4 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.4.3

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SI-16 Memory Protection
addresses: CWE-416

Use-after-free exploits that achieve arbitrary code execution are blocked or significantly hardened by non-executable pages and ASLR.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure SDLC practices directly prevent double-free errors via static analysis, safe memory APIs, and testing.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover use-after-free issues via scanning or analysis but do not prevent their introduction.

PR.PS-02 partial match
prevents

Routine patching removes known use-after-free instances after they have been introduced in released software.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development can detect use-after-free bugs before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates memory-safety practices that reduce use-after-free defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify memory-management rules that mitigate use-after-free.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include memory-safety design choices that limit use-after-free exposure.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prescribe avoidance of use-after-free patterns.

A.8.32 Change management partial match
prevents

Change-management processes help ensure memory-safety fixes are deployed consistently.

References