LiveActive security incident?Get immediate response
CVE Record

CVE-2011-2702: Integer signedness error in Glibc before 2.13 and eglibc before 2.13, when using Supplemental Streaming SIM...

Integer signedness error in Glibc before 2.13 and eglibc before 2.13, when using Supplemental Streaming SIMD Extensions 3 (SSSE3) optimization, allows context-dependent attackers to execute arbitrary code via a negative length parameter to (1) memcpy-ssse3-rep.S, (2) memcpy-ssse3.S, or (3) memset-sse2.S in sysdeps/i386/i686/multiarch/, which triggers an out-of-bounds read, as demonstrated using the memcpy function.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old memory-safety flaw in glibc/eglibc, the C library used by many Linux systems. On affected pre-2.13 builds using specific x86 optimized routines, a bad negative length value could corrupt memory and may allow arbitrary code execution. The main business risk is unsupported legacy Linux, appliances, containers, or embedded systems still carrying these libraries. Exposure is most plausible on legacy 32-bit x86 Linux systems, old base images, embedded devices, or appliances using glibc/eglibc before 2.13. Current maintained distributions are unlikely to ship these vulnerable library versions, but inherited binaries and frozen images need verification. Treat this as a legacy exposure cleanup item with high impact if present. It should not displace actively exploited modern vulnerabilities unless your environment still includes old Linux appliances, embedded systems, or frozen images that process untrusted input. Mitigation focus: Inventory Linux hosts, containers, appliances, and embedded images for glibc or eglibc versions.; Upgrade affected glibc/eglibc packages to vendor-fixed releases, preferably 2.13 or later lineage.; Check distribution security advisories for backported fixes when version strings remain below 2.13..

Prepared

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-2011-2702 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
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
3Source links

CVSS and timeline data

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

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.