CVE-2005-2972: n/a vulnerability

CVE-2005-2972: Multiple stack-based buffer overflows in the RTF import feature in AbiWord before 2.2.11 allow user-assiste...

Multiple stack-based buffer overflows in the RTF import feature in AbiWord before 2.2.11 allow user-assisted attackers to execute arbitrary code via an RTF file with long identifiers, which are not properly handled in the (1) ParseLevelText, (2) getCharsInsideBrace, (3) HandleLists, (4) or (5) HandleAbiLists functions in ie_imp_RTF.cpp, a different vulnerability than CVE-2005-2964.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 22:53 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2005-2972 is an old AbiWord document-processing flaw. A crafted RTF file with overly long identifiers could crash the parser or potentially run code when a user opens it. Business risk is mainly to legacy desktops or environments that still allow outdated AbiWord to handle untrusted RTF documents. Exposure is most likely on legacy Linux or Unix desktop systems, archived appliances, or long-lived images still running AbiWord earlier than 2.2.11. Current managed endpoints are unlikely to be affected unless old AbiWord packages remain installed or are used to process user-supplied RTF files. Treat this as a targeted legacy-software cleanup item, not an internet-wide emergency. Prioritize environments that process externally supplied documents or preserve old desktop images. If no vulnerable AbiWord exists, residual risk is low. Mitigation focus: Upgrade AbiWord to 2.2.11 or a vendor-fixed distribution package.; Remove AbiWord where it is not operationally required.; Prevent vulnerable AbiWord from opening untrusted RTF files..

Prepared: Jun 29, 2026, 17:30 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2005-2972 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Oct 23, 2005, 04:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
USN-203-1CVE reference · vendor-advisory, x_refsource_UBUNTU

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.