LiveActive security incident?Get immediate response
CVE Record

CVE-2018-11237: An AVX-512-optimized implementation of the mempcpy function in the GNU C Library (aka glibc or libc6) 2.27...

An AVX-512-optimized implementation of the mempcpy function in the GNU C Library (aka glibc or libc6) 2.27 and earlier may write data beyond the target buffer, leading to a buffer overflow in __mempcpy_avx512_no_vzeroupper.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-11237 is a glibc memory-copy bug. In affected versions, a specialized AVX-512 mempcpy path can write past the destination buffer, creating a buffer overflow risk in software that reaches that code path.

Executive priority

Treat this as a high-priority platform patching issue, not a standalone application bug. Exposure may be broad because glibc is foundational, but confirmed urgency depends on deployed versions and vendor guidance.

Technical view

The issue is in __mempcpy_avx512_no_vzeroupper, an AVX-512-optimized mempcpy implementation in GNU C Library 2.27 and earlier. The source bundle states it may write beyond the target buffer. Vendor advisories from Red Hat, Ubuntu, Oracle, and NetApp indicate downstream exposure was assessed or patched.

Likely exposure

Linux systems and products bundling glibc/libc6 2.27 or earlier may be exposed, especially where AVX-512-capable execution paths are possible. Exact product exposure depends on vendor packaging and advisories.

Exploitation context

The bundle includes an Exploit-DB reference, so public exploit information existed. KEV is false, and the provided sources do not establish active exploitation in the wild.

Researcher notes

Evidence is limited to the CVE description and referenced advisories. The key condition is the AVX-512 mempcpy implementation in glibc 2.27 and earlier. Do not assume exploitability for every application using glibc without validating code path, platform, and vendor package state.

Mitigation direction

  • Apply vendor glibc/libc6 updates from the relevant Linux or product vendor.
  • Review Red Hat, Ubuntu, Oracle, and NetApp advisories for product-specific applicability.
  • Prioritize internet-facing, multi-user, and high-trust workloads using affected glibc builds.
  • If no vendor fix is available, follow vendor guidance for compensating controls.

Validation and detection

  • Inventory systems for glibc/libc6 versions at or before 2.27.
  • Map affected systems to Red Hat, Ubuntu, Oracle, or NetApp advisory coverage.
  • Confirm whether updates replacing vulnerable glibc packages are installed.
  • Record systems where vendor applicability is unclear for manual review.
Prepared
Confidence
medium
Sources
9

Public sources used

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-2018-11237 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
9Source links

CVSS and timeline data

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

Source materials

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.