cve.bz

CVE-2023-1355 vim vim: NULL Pointer Dereference

5.5 mediumExploit referenceEPSS 0.5%Fix available

Medium (5.5) in vim vim. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
NULL Pointer Dereference in GitHub repository vim/vim prior to 9.0.1402.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2025-02-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-1355 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-1355?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-1355?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-1355 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
vim/vimbefore 9.0.1402

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12vimno fix listedDEBIAN-CVE-2023-1355
Debian13, 14vim2:9.0.1658-1DEBIAN-CVE-2023-1355
SUSELinux Enterprise Micro 5.1, Linux Enterprise Micro 5.2, Linux Enterprise Micro 5.3 and 4 morevim9.0.1443-150000.5.40.1SUSE-SU-2023:2103-1
SUSELinux Enterprise Server 12 SP2-BCL, Linux Enterprise Server 12 SP5, Linux Enterprise Server for SAP Applications 12 SP5vim9.0.1572-17.18.1SUSE-SU-2023:3463-1
openSUSELeap 15.4, Leap Micro 5.3vim9.0.1443-150000.5.40.1SUSE-SU-2023:2103-1
openSUSETumbleweedvim9.0.1430-1.1openSUSE-SU-2024:12832-1
Alpinev3.18, v3.19, v3.20 and 4 morevim9.0.1395-r0ALPINE-CVE-2023-1355
Alpaquita23vim9.1.0936-r0BELL-CVE-2023-1355

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

Red Hat Product Security has rated this issue as having a Low security impact, because the "victim" has to run an untrusted file IN SCRIPT MODE. Someone who is running untrusted files in script mode is equivalent to someone just taking a random python script and running it.

For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ and Red Hat Enterprise Linux Life Cycle & Updates Policy: https://access.redhat.com/support/policy/updates/errata/.

Red Hat's mitigation

Untrusted vim scripts with -s [scriptin] are not recommended to run.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6vimNot affected
Red Hat Enterprise Linux 7vimNot affected
Red Hat Enterprise Linux 8vimNot affected
Red Hat Enterprise Linux 9vimNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-1355.

References

Check your stackJSON