CVE-2010-3192

glibc: __fortify_fail may use corrupted memory when called from SSP callback

Published Oct 12, 2010 CVSS 2.0 · 5.0 Medium EPSS 1.6% KEV · Not listed
Description
Certain run-time memory protection mechanisms in the GNU C Library (aka glibc or libc6) print argv[0] and backtrace information, which might allow context-dependent attackers to obtain sensitive information from process memory by executing an incorrect program, as demonstrated by a setuid program that contains a stack-based buffer overflow error, related to the __fortify_fail function in debug/fortify_fail.c, and the __stack_chk_fail (aka stack protection) and __chk_fail (aka FORTIFY_SOURCE) implementations.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2010-3192 Certain run-time memory protection mechanisms in the GNU C Library (aka glibc or libc6) print argv[0] and backtrace information, which might allow context-dependent attackers to obtain sensitive information from process memory by executing an incorrect program, as demonstrated by a setuid program that contains a stack-based buffer overflow error, related to the __fortify_fail function in debug/fortify_fail.c, and the __stack_chk_fail (aka stack protection) and __chk_fail (aka FORTIFY_SOURCE) implementations.
Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Sep 16, 2024, 4:17 PM
Reserved
Aug 31, 2010, 12:00 AM
Status
Modified
Published
Oct 14, 2010, 5:58 AM
Modified
Jun 16, 2026, 11:22 PM
Severity
Low
Public date
Apr 27, 2010, 12:00 AM