CVE-2008-2664: n/a vulnerability

CVE-2008-2664: The rb_str_format function in Ruby 1.8.4 and earlier, 1.8.5 before 1.8.5-p231, 1.8.6 before 1.8.6-p230, 1.8...

The rb_str_format function in Ruby 1.8.4 and earlier, 1.8.5 before 1.8.5-p231, 1.8.6 before 1.8.6-p230, 1.8.7 before 1.8.7-p22, and 1.9.0 before 1.9.0-2 allows context-dependent attackers to trigger memory corruption via unspecified vectors related to alloca, a different issue than CVE-2008-2662, CVE-2008-2663, and CVE-2008-2725. NOTE: as of 20080624, there has been inconsistent usage of multiple CVE identifiers related to Ruby. The CVE description should be regarded as authoritative, although it is likely to change.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 09:05 UTC (UTC+00:00)

Security readout for executives and security teams

This is an old Ruby runtime memory-corruption flaw in string formatting. Systems still running the listed 2008-era Ruby versions may be exposed, especially legacy applications or vendor appliances. The bundle does not show active exploitation or a modern CVSS score. Likely exposure is limited to unsupported legacy Ruby deployments, embedded Ruby runtimes, old Linux distribution packages, or archived application stacks not rebuilt since 2008. Treat this as a legacy-risk cleanup item with high potential impact but uncertain current exploitability. Prioritize internet-facing or business-critical systems still using old Ruby. Mitigation focus: Identify all Ruby runtimes and package versions in production and legacy environments.; Upgrade past the fixed Ruby versions named in the CVE description.; Apply relevant vendor distribution updates from Debian, SUSE, Mandriva, Slackware, or Apple where applicable..

Prepared: Jun 28, 2026, 18:52 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-2664 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: Jun 24, 2008, 19: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

5Source 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
ruby-rbstrformat-code-execution(43348)CVE reference · vdb-entry, x_refsource_XF
FEDORA-2008-5649CVE reference · vendor-advisory, x_refsource_FEDORA
oval:org.mitre.oval:def:9646CVE reference · vdb-entry, signature
https://issues.rpath.com/browse/RPL-2626CVE reference · x_refsource_CONFIRM

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.