CVE-2008-5031: n/a vulnerability

CVE-2008-5031: Multiple integer overflows in Python 2.2.3 through 2.5.1, and 2.6, allow context-dependent attackers to hav...

Multiple integer overflows in Python 2.2.3 through 2.5.1, and 2.6, allow context-dependent attackers to have an unknown impact via a large integer value in the tabsize argument to the expandtabs method, as implemented by (1) the string_expandtabs function in Objects/stringobject.c and (2) the unicode_expandtabs function in Objects/unicodeobject.c. NOTE: this vulnerability reportedly exists because of an incomplete fix for CVE-2008-2315.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 10:40 UTC (UTC+00:00)

Security readout for executives and security teams

This is an old Python runtime flaw involving very large tab-size values passed to string expansion functions. The published record says the impact is unknown. It matters mainly where legacy Python versions remain embedded in applications, operating systems, or appliances that process attacker-influenced input. Exposure is most plausible in legacy systems still running affected Python 2 versions, including vendor-bundled Python in products referenced by Gentoo, Apple, and VMware advisories. Modern supported Python deployments are unlikely to be affected by this specific historical issue. Prioritize as legacy risk management unless affected Python is reachable through exposed services or untrusted input processing. The incomplete impact data prevents a confident severity call, but unsupported runtimes should be remediated as operational debt. Mitigation focus: Inventory Python runtimes and embedded vendor packages.; Upgrade affected Python versions through supported vendor packages.; Check Gentoo, Apple, VMware, and application vendor advisories..

Prepared: Jun 28, 2026, 18:15 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.

cve · low confidence lookup

CVE-2008-5031 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: Nov 10, 2008, 16: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

4Source 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
python-expandtabs-integer-overflow(46612)CVE reference · vdb-entry, x_refsource_XF
oval:org.mitre.oval:def:8564CVE reference · vdb-entry, signature
oval:org.mitre.oval:def:11280CVE reference · vdb-entry, signature

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.