Vulnerability-Lookup

OESA-2024-2115 (CVE-2024-43802)

Vulnerability from osv_openeuler – Published: 2024-09-06 11:07 – Updated: 2026-08-06 11:07 – Source website

Summary

vim security update

Details

Vim is an advanced text editor that seeks to provide the power of the de-facto Unix editor 'Vi', with a more complete feature set. Vim is a highly configurable text editor built to enable efficient text editing. It is an improved version of the vi editor distributed with most UNIX systems.

Security Fix(es):

Vim is an improved version of the unix vi text editor. When flushing the typeahead buffer, Vim moves the current position in the typeahead buffer but does not check whether there is enough space left in the buffer to handle the next characters. So this may lead to the tb_off position within the typebuf variable to point outside of the valid buffer size, which can then later lead to a heap-buffer overflow in e.g. ins_typebuf(). Therefore, when flushing the typeahead buffer, check if there is enough space left before advancing the off position. If not, fall back to flush current typebuf contents. It's not quite clear yet, what can lead to this situation. It seems to happen when error messages occur (which will cause Vim to flush the typeahead buffer) in comnination with several long mappgins and so it may eventually move the off position out of a valid buffer size. Impact is low since it is not easily reproducible and requires to have several mappings active and run into some error condition. But when this happens, this will cause a crash. The issue has been fixed as of Vim patch v9.1.0697. Users are advised to upgrade. There are no known workarounds for this issue.(CVE-2024-43802)

Severity

4.5 (Medium)


                    
                      CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

References

URL

Type

	https://www.openeuler.org/zh/security/security-bu…	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2024-43802	ADVISORY

JSON

To clipboard

{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "vim-X11-9.0-27.oe2203sp4.aarch64.rpm",
          "vim-common-9.0-27.oe2203sp4.aarch64.rpm",
          "vim-debuginfo-9.0-27.oe2203sp4.aarch64.rpm",
          "vim-debugsource-9.0-27.oe2203sp4.aarch64.rpm",
          "vim-enhanced-9.0-27.oe2203sp4.aarch64.rpm",
          "vim-minimal-9.0-27.oe2203sp4.aarch64.rpm"
        ],
        "noarch": [
          "vim-filesystem-9.0-27.oe2203sp4.noarch.rpm"
        ],
        "src": [
          "vim-9.0-27.oe2203sp4.src.rpm"
        ],
        "x86_64": [
          "vim-X11-9.0-27.oe2203sp4.x86_64.rpm",
          "vim-common-9.0-27.oe2203sp4.x86_64.rpm",
          "vim-debuginfo-9.0-27.oe2203sp4.x86_64.rpm",
          "vim-debugsource-9.0-27.oe2203sp4.x86_64.rpm",
          "vim-enhanced-9.0-27.oe2203sp4.x86_64.rpm",
          "vim-minimal-9.0-27.oe2203sp4.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:22.03-LTS-SP4",
        "name": "vim",
        "purl": "pkg:rpm/openEuler/vim\u0026distro=openEuler-22.03-LTS-SP4"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "9.0-27.oe2203sp4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "vim-X11-9.0-27.oe2203sp3.aarch64.rpm",
          "vim-common-9.0-27.oe2203sp3.aarch64.rpm",
          "vim-debuginfo-9.0-27.oe2203sp3.aarch64.rpm",
          "vim-debugsource-9.0-27.oe2203sp3.aarch64.rpm",
          "vim-enhanced-9.0-27.oe2203sp3.aarch64.rpm",
          "vim-minimal-9.0-27.oe2203sp3.aarch64.rpm"
        ],
        "noarch": [
          "vim-filesystem-9.0-27.oe2203sp3.noarch.rpm"
        ],
        "src": [
          "vim-9.0-27.oe2203sp3.src.rpm"
        ],
        "x86_64": [
          "vim-X11-9.0-27.oe2203sp3.x86_64.rpm",
          "vim-common-9.0-27.oe2203sp3.x86_64.rpm",
          "vim-debuginfo-9.0-27.oe2203sp3.x86_64.rpm",
          "vim-debugsource-9.0-27.oe2203sp3.x86_64.rpm",
          "vim-enhanced-9.0-27.oe2203sp3.x86_64.rpm",
          "vim-minimal-9.0-27.oe2203sp3.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:22.03-LTS-SP3",
        "name": "vim",
        "purl": "pkg:rpm/openEuler/vim\u0026distro=openEuler-22.03-LTS-SP3"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "9.0-27.oe2203sp3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "vim-X11-9.0-26.oe2003sp4.aarch64.rpm",
          "vim-common-9.0-26.oe2003sp4.aarch64.rpm",
          "vim-debuginfo-9.0-26.oe2003sp4.aarch64.rpm",
          "vim-debugsource-9.0-26.oe2003sp4.aarch64.rpm",
          "vim-enhanced-9.0-26.oe2003sp4.aarch64.rpm",
          "vim-minimal-9.0-26.oe2003sp4.aarch64.rpm"
        ],
        "noarch": [
          "vim-filesystem-9.0-26.oe2003sp4.noarch.rpm"
        ],
        "src": [
          "vim-9.0-26.oe2003sp4.src.rpm"
        ],
        "x86_64": [
          "vim-X11-9.0-26.oe2003sp4.x86_64.rpm",
          "vim-common-9.0-26.oe2003sp4.x86_64.rpm",
          "vim-debuginfo-9.0-26.oe2003sp4.x86_64.rpm",
          "vim-debugsource-9.0-26.oe2003sp4.x86_64.rpm",
          "vim-enhanced-9.0-26.oe2003sp4.x86_64.rpm",
          "vim-minimal-9.0-26.oe2003sp4.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP4",
        "name": "vim",
        "purl": "pkg:rpm/openEuler/vim\u0026distro=openEuler-20.03-LTS-SP4"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "9.0-26.oe2003sp4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "vim-X11-9.0-27.oe2203sp1.aarch64.rpm",
          "vim-common-9.0-27.oe2203sp1.aarch64.rpm",
          "vim-debuginfo-9.0-27.oe2203sp1.aarch64.rpm",
          "vim-debugsource-9.0-27.oe2203sp1.aarch64.rpm",
          "vim-enhanced-9.0-27.oe2203sp1.aarch64.rpm",
          "vim-minimal-9.0-27.oe2203sp1.aarch64.rpm"
        ],
        "noarch": [
          "vim-filesystem-9.0-27.oe2203sp1.noarch.rpm"
        ],
        "src": [
          "vim-9.0-27.oe2203sp1.src.rpm"
        ],
        "x86_64": [
          "vim-X11-9.0-27.oe2203sp1.x86_64.rpm",
          "vim-common-9.0-27.oe2203sp1.x86_64.rpm",
          "vim-debuginfo-9.0-27.oe2203sp1.x86_64.rpm",
          "vim-debugsource-9.0-27.oe2203sp1.x86_64.rpm",
          "vim-enhanced-9.0-27.oe2203sp1.x86_64.rpm",
          "vim-minimal-9.0-27.oe2203sp1.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:22.03-LTS-SP1",
        "name": "vim",
        "purl": "pkg:rpm/openEuler/vim\u0026distro=openEuler-22.03-LTS-SP1"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "9.0-27.oe2203sp1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "vim-X11-9.0.2092-11.oe2403.aarch64.rpm",
          "vim-common-9.0.2092-11.oe2403.aarch64.rpm",
          "vim-debuginfo-9.0.2092-11.oe2403.aarch64.rpm",
          "vim-debugsource-9.0.2092-11.oe2403.aarch64.rpm",
          "vim-enhanced-9.0.2092-11.oe2403.aarch64.rpm",
          "vim-minimal-9.0.2092-11.oe2403.aarch64.rpm"
        ],
        "noarch": [
          "vim-filesystem-9.0.2092-11.oe2403.noarch.rpm"
        ],
        "src": [
          "vim-9.0.2092-11.oe2403.src.rpm"
        ],
        "x86_64": [
          "vim-X11-9.0.2092-11.oe2403.x86_64.rpm",
          "vim-common-9.0.2092-11.oe2403.x86_64.rpm",
          "vim-debuginfo-9.0.2092-11.oe2403.x86_64.rpm",
          "vim-debugsource-9.0.2092-11.oe2403.x86_64.rpm",
          "vim-enhanced-9.0.2092-11.oe2403.x86_64.rpm",
          "vim-minimal-9.0.2092-11.oe2403.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:24.03-LTS",
        "name": "vim",
        "purl": "pkg:rpm/openEuler/vim\u0026distro=openEuler-24.03-LTS"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "9.0.2092-11.oe2403"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "Medium"
  },
  "details": "Vim is an advanced text editor that seeks to provide the power of the de-facto Unix editor \u0026apos;Vi\u0026apos;, with a more complete feature set. Vim is a highly configurable text editor built to enable efficient text editing. It is an improved version of the vi editor distributed with most UNIX systems.\n\nSecurity Fix(es):\n\nVim is an improved version of the unix vi text editor. When flushing the typeahead buffer, Vim moves the current position in the typeahead buffer but does not check whether there is enough space left in the buffer to handle the next characters.  So this may lead to the tb_off position within the typebuf variable to point outside of the valid buffer size, which can then later lead to a heap-buffer overflow in e.g. ins_typebuf(). Therefore, when flushing the typeahead buffer, check if there is enough space left before advancing the off position. If not, fall back to flush current typebuf contents. It\u0026apos;s not quite clear yet, what can lead to this situation. It seems to happen when error messages occur (which will cause Vim to flush the typeahead buffer) in comnination with several long mappgins and so it may eventually move the off position out of a valid buffer size. Impact is low since it is not easily reproducible and requires to have several mappings active and run into some error condition. But when this happens, this will cause a crash. The issue has been fixed as of Vim patch v9.1.0697. Users are advised to upgrade. There are no known workarounds for this issue.(CVE-2024-43802)",
  "id": "OESA-2024-2115",
  "modified": "2026-08-06T11:07:35Z",
  "published": "2024-09-06T11:07:35Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2115"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43802"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "vim security update",
  "upstream": [
    "CVE-2024-43802"
  ]
}

CVE-2024-43802 (GCVE-0-2024-43802)

Vulnerability from cvelistv5 – Published: 2024-08-26 18:48 – Updated: 2025-11-03 20:38

Title

heap-buffer-overflow in ins_typebuf() in Vim < 9.1.0697

Summary

Severity

4.5 (Medium)


                        
                          CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

SSVC

Exploitation: none Automatable: no Technical Impact: partial

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2024-08-28 14:28 UTC

CWE

CWE-122 - Heap-based Buffer Overflow

Assigner

GitHub_M CNA under the mitre root

CNA scorecard C 72/100 over 7843 records in the last 180 days details

References

4 references

URL	Tags
https://github.com/vim/vim/security/advisories/GH…	x_refsource_CONFIRM
https://github.com/vim/vim/commit/322ba9108612bead5eb	x_refsource_MISC
https://security.netapp.com/advisory/ntap-2024100…
https://lists.debian.org/debian-lts-announce/2025…

Impacted products

1 product

Vendor	Product	Version
vim	vim	Affected: < 9.1.0697

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-43802",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-08-28T14:28:07.231057Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-08-28T14:28:30.371Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2025-11-03T20:38:52.392Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "https://security.netapp.com/advisory/ntap-20241004-0008/"
          },
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/03/msg00023.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "vim",
          "vendor": "vim",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 9.1.0697"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Vim is an improved version of the unix vi text editor. When flushing the typeahead buffer, Vim moves the current position in the typeahead buffer but does not check whether there is enough space left in the buffer to handle the next characters.  So this may lead to the tb_off position within the typebuf variable to point outside of the valid buffer size, which can then later lead to a heap-buffer overflow in e.g. ins_typebuf(). Therefore, when flushing the typeahead buffer, check if there is enough space left before advancing the off position. If not, fall back to flush current typebuf contents. It\u0027s not quite clear yet, what can lead to this situation. It seems to happen when error messages occur (which will cause Vim to flush the typeahead buffer) in comnination with several long mappgins and so it may eventually move the off position out of a valid buffer size. Impact is low since it is not easily reproducible and requires to have several mappings active and run into some error condition. But when this happens, this will cause a crash. The issue has been fixed as of Vim patch v9.1.0697. Users are advised to upgrade. There are no known workarounds for this issue."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "LOCAL",
            "availabilityImpact": "LOW",
            "baseScore": 4.5,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-122",
              "description": "CWE-122: Heap-based Buffer Overflow",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-08-26T18:48:11.979Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/vim/vim/security/advisories/GHSA-4ghr-c62x-cqfh",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/vim/vim/security/advisories/GHSA-4ghr-c62x-cqfh"
        },
        {
          "name": "https://github.com/vim/vim/commit/322ba9108612bead5eb",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/vim/vim/commit/322ba9108612bead5eb"
        }
      ],
      "source": {
        "advisory": "GHSA-4ghr-c62x-cqfh",
        "discovery": "UNKNOWN"
      },
      "title": "heap-buffer-overflow in ins_typebuf() in Vim \u003c 9.1.0697"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2024-43802",
    "datePublished": "2024-08-26T18:48:11.979Z",
    "dateReserved": "2024-08-16T14:20:37.326Z",
    "dateUpdated": "2025-11-03T20:38:52.392Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted