🛡️ USN-5460-1 — vim

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

vim vulnerabilities

It was discovered that Vim was incorrectly processing Vim buffers.

An attacker could possibly use this issue to perform illegal memory

access and expose sensitive information. (CVE-2022-0554)

It was discovered that Vim was not properly performing bounds checks

for column numbers when replacing tabs with spaces or spaces with

tabs, which could cause a heap buffer overflow. An attacker could

possibly use this issue to cause a denial of service or execute

arbitrary code. (CVE-2022-0572)

It was discovered that Vim was not properly performing validation of

data that contained special multi-byte characters, which could cause

an out-of-bounds read. An attacker could possibly use this issue to

cause a denial of service. (CVE-2022-0685)

It was discovered that Vim was incorrectly processing data used to

define indentation in a file, which could cause a heap buffer

overflow. An attacker could possibly use this issue to cause a denial

of service. (CVE-2022-0714)

It was discovered that Vim was incorrectly processing certain regular

expression patterns and strings, which could cause an out-of-bounds

read. An attacker could possibly use this issue to cause a denial of

service. (CVE-2022-0729)

It was discovered that Vim was not properly performing bounds checks

when executing spell suggestion commands, which could cause a heap

buffer overflow. An attacker could possibly use this issue to cause a

denial of service or execute arbitrary code. (CVE-2022-0943)

It was discovered that Vim was incorrectly performing bounds checks

when processing invalid commands with composing characters in Ex

mode, which could cause a buffer overflow. An attacker could possibly

use this issue to cause a denial of service or execute arbitrary

code. (CVE-2022-1616)

It was discovered that Vim was not properly processing latin1 data

when issuing Ex commands, which could cause a heap buffer overflow.

An attacker could possibly use this issue to cause a denial of

service or execute arbitrary code. (CVE-2022-1619)

It was discovered that Vim was not properly performing memory

management when dealing with invalid regular expression patterns in

buffers, which could cause a NULL pointer dereference. An attacker

could possibly use this issue to cause a denial of service.

(CVE-2022-1620)

It was discovered that Vim was not properly processing invalid bytes

when performing spell check operations, which could cause a heap

buffer overflow. An attacker could possibly use this issue to cause a

denial of service or execute arbitrary code. (CVE-2022-1621)

Affected software

USN-5460-1 is recorded against 1 package.

  • vim (fixed in 2:7.4.1689-3ubuntu1.5+esm6)

Timeline and source

Published on 6 June 2022 and last revised on 25 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

ubuntu.com (Advisory)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2022-06-06
Updated 2026-08-12
Modified 2026-06-25
Fix URL N/A

Affected Packages

Software From version Fixed in
vim 2:7.4.1689-3ubuntu1.5+esm6

Free Vulnerability Check

Is your site affected by USN-5460-1?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against USN-5460-1 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.