Severity

Medium

Vendor

Canonical Ubuntu

Versions Affected

• Canonical Ubuntu 16.04
• Canonical Ubuntu 18.04
• Canonical Ubuntu 22.04

Description

It was discovered that Vim incorrectly handled memory when opening certain files. If an attacker could trick a user into opening a specially crafted file, it could cause Vim to crash, or possibly execute arbitrary code. This issue only affected Ubuntu 22.04 LTS. (CVE-2022-2182) It was discovered that Vim incorrectly handled memory when deleting buffers in diff mode. An attacker could possibly use this issue to cause a denial of service. This issue only affected Ubuntu 20.04 LTS and Ubuntu 22.04 LTS. (CVE-2022-2208) It was discovered that Vim incorrectly handled memory access. An attacker could possibly use this issue to cause the corruption of sensitive information, a crash, or arbitrary code execution. This issue only affected Ubuntu 14.04 LTS, Ubuntu 18.04 LTS, Ubuntu 20.04 LTS and Ubuntu 22.04 LTS. (CVE-2022-2210) It was discovered that Vim incorrectly handled memory when using nested :source. An attacker could possibly use this issue to cause a denial of service. This issue only affected Ubuntu 22.04 LTS. (CVE-2022-2231) It was discovered that Vim did not properly perform bounds checks when processing a menu item with the only modifier. An attacker could possibly use this issue to cause a denial of service. (CVE-2022-2257) It was discovered that Vim incorrectly handled memory when opening certain files. If an attacker could trick a user into opening a specially crafted file, it could cause Vim to crash, or possibly execute arbitrary code. (CVE-2022-2264, CVE-2022-2284, CVE-2022-2289) It was discovered that Vim did not properly perform bounds checks when going over the end of the typahead. An attacker could possibly use this issue to cause a denial of service. (CVE-2022-2285) It was discovered that Vim did not properly perform bounds checks when reading the provided string. An attacker could possibly use this issue to cause a denial of service. (CVE-2022-2286) It was discovered that Vim incorrectly handled memory when adding words with a control character to the internal spell word list. An attacker could possibly use this issue to cause a denial of service. (CVE-2022-2287) Update Instructions: Run sudo pro fix USN-6270-1 to fix the vulnerability. The problem can be corrected by updating your system to the following package versions: vim-common – 2:8.2.3995-1ubuntu2.10 vim-athena – 2:8.2.3995-1ubuntu2.10 vim-tiny – 2:8.2.3995-1ubuntu2.10 vim-gtk – 2:8.2.3995-1ubuntu2.10 vim-gui-common – 2:8.2.3995-1ubuntu2.10 vim – 2:8.2.3995-1ubuntu2.10 vim-doc – 2:8.2.3995-1ubuntu2.10 xxd – 2:8.2.3995-1ubuntu2.10 vim-runtime – 2:8.2.3995-1ubuntu2.10 vim-gtk3 – 2:8.2.3995-1ubuntu2.10 vim-nox – 2:8.2.3995-1ubuntu2.10 No subscription required

CVEs contained in this USN include: CVE-2022-2182, CVE-2022-2208, CVE-2022-2210, CVE-2022-2231, CVE-2022-2257, CVE-2022-2264, CVE-2022-2284, CVE-2022-2285, CVE-2022-2286, CVE-2022-2287, CVE-2022-2289.

Affected Cloud Foundry Products and Versions

Severity is medium unless otherwise noted.

• cflinuxfs4
  • All versions prior to 1.28.0
• Jammy Stemcells
  • 1.x versions prior to 1.199
  • All other stemcells not listed.
• CF Deployment
  • All versions prior to 30.0.0, or later versions with Jammy Stemcells prior to 1.199

Mitigation

Users of affected products are strongly encouraged to follow the mitigations below.

The Cloud Foundry project recommends upgrading the following releases:

• Bionic Stemcells
  • There are no fixed versions of this product
  • All other stemcells should be upgraded to the latest version available on bosh.io.
• cflinuxfs4
  • Upgrade all versions to 1.28.0 or greater
• Jammy Stemcells
  • Upgrade 1.x versions to 1.199 or greater
  • All other stemcells should be upgraded to the latest version available on bosh.io.
• CF Deployment
  • Upgrade all versions to 30.0.0 or greater and upgrade Jammy Stemcells to 1.199 or greater

References

• USN Notice
• CVE-2022-2182
• CVE-2022-2208
• CVE-2022-2210
• CVE-2022-2231
• CVE-2022-2257
• CVE-2022-2264
• CVE-2022-2284
• CVE-2022-2285
• CVE-2022-2286
• CVE-2022-2287
• CVE-2022-2289

History

2023-10-05: Initial vulnerability report published.