Cloudanix VulnDB

CVE-2015-8983

High · 8.1

CVSS

8.1

EPSS

4.0%

Published

Mar 20, 2017

CISA due date

—

Cloudanix analysis

Next patch cycle SSVC: Track

A flaw in a core system library used by many programs can let attackers crash applications or take control of computers by sending specially crafted data.

Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
High
Impact
Remote Code Execution
Component
Library
Class
Buffer Overflow
Remediation
Upgrade
Effort
Medium
Patch risk
Medium

What it actually does

Integer overflow in _IO_wstr_overflow allows computation of an undersized buffer allocation that triggers a subsequent heap-based buffer overflow during wide-string operations.

Why it matters to the business

Applications linked against vulnerable glibc versions may crash or allow remote code execution, leading to service outages or full system compromise on affected Linux systems; the flaw has existed in the ecosystem for years with low but persistent exploitability.

How an attack unfolds

An attacker supplies specially crafted wide-character input that forces the library to miscalculate a required buffer size; the resulting undersized allocation is then overflowed when data is written, allowing control of adjacent heap structures and potential arbitrary code execution.

How to fix it

Upgrade the GNU C Library to version 2.22 or later on all affected systems; rebuild and restart any statically linked applications; apply vendor-supplied patches for distributions still shipping older glibc releases.

How to confirm the fix worked

Confirm glibc version is 2.22 or newer via ldd --version or rpm/dpkg queries; test affected applications with known triggering inputs in a lab environment; monitor for absence of crashes under load after patching.

Typical attack path

  1. Identify a network-facing or local application that uses glibc wide-string I/O routines
  2. Craft input that triggers the integer overflow in size calculation within _IO_wstr_overflow
  3. Trigger the heap buffer overflow to corrupt memory metadata
  4. Achieve code execution or denial of service depending on attacker goals and memory layout

How to detect it

Search application and system logs for segmentation faults or heap corruption messages originating from processes linked to glibc versions older than 2.22; correlate with inbound network traffic containing wide-character sequences; no public exploit artifacts are widely available for this older issue.

What your security team should do

  • Prioritize patching glibc on internet-facing systems and those processing untrusted wide-character data
  • Inventory statically linked binaries that embed vulnerable glibc versions
  • Add glibc version checks to vulnerability scanning and asset-management processes
  • Review logs for application crashes that coincide with unusual input patterns as a temporary detection measure

The record

Integer overflow in the _IO_wstr_overflow function in libio/wstrops.c in the GNU C Library (aka glibc or libc6) before 2.22 allows context-dependent attackers to cause a denial of service (application crash) or possibly execute arbitrary code via vectors related to computing a size in bytes, which triggers a heap-based buffer overflow.

Affected packages

Ecosystem Package Introduced Fixed
Debian:11 glibc 0 2.21-1
Debian:12 glibc 0 2.21-1
Debian:13 glibc 0 2.21-1
Debian:6.0 eglibc 0 2.11.3-4+deb6u7
SUSE:Linux Enterprise Point of Sale 11 SP3 glibc 0 2.11.3-17.110.40.1
SUSE:Linux Enterprise Server 11 SP4-LTSS glibc 0 2.11.3-17.110.40.1
Ubuntu:14.04:LTS eglibc 0 2.19-0ubuntu6.10
Ubuntu:16.04:LTS glibc 0 2.23-0ubuntu3
Ubuntu:16.04:LTS glibc 0 2.23-0ubuntu6

Related vulnerabilities