SecurityTracker.com
    Home    |    View Topics    |    Search    |    Contact Us    |   

SecurityTracker
Archives


 


Category:   Application (Generic)  >   Glibc Vendors:   GNU [multiple authors]
Glibc Memory Corruption Flaw in fnmatch() May Let Remote Users Execute Arbitrary Code
SecurityTracker Alert ID:  1025290
SecurityTracker URL:  http://securitytracker.com/id/1025290
CVE Reference:   CVE-2011-1071   (Links to External Site)
Date:  Apr 5 2011
Impact:   Execution of arbitrary code via network, User access via network
Fix Available:  Yes  Vendor Confirmed:  Yes  

Description:   A vulnerability was reported in glibc. A remote user may be able to execute arbitrary code on the target system.

A remote user can send specially crafted UTF8 data to an application that uses the fnmatch() function to potentially execute arbitrary code on the target system. The code will run with the privileges of the target service.

Impact:   A remote user may be able to execute arbitrary code on the target system.
Solution:   The vendor has issued a source code fix, available at:

http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f15ce4d8dc139523fe0c273580b604b2453acba6

Vendor URL:  www.gnu.org/software/libc/ (Links to External Site)
Cause:   Access control error
Underlying OS:  Linux (Any)

Message History:   This archive entry has one or more follow-up message(s) listed below.
Apr 5 2011 (Red Hat Issues Fix) Glibc Memory Corruption Flaw in fnmatch() May Let Remote Users Execute Arbitrary Code
Red Hat has issued a fix for Red Hat Enterprise Linux 5.
Apr 5 2011 (Red Hat Issues Fix) Glibc Memory Corruption Flaw in fnmatch() May Let Remote Users Execute Arbitrary Code
Red Hat has issued a fix for Red Hat Enterprise Linux 6.
Jul 29 2011 (VMware Issues Fix for ESX) Glibc Memory Corruption Flaw in fnmatch() May Let Remote Users Execute Arbitrary Code
VMware has issued a fix for VMware ESX.
Feb 14 2012 (Red Hat Issues Fix) Glibc Memory Corruption Flaw in fnmatch() May Let Remote Users Execute Arbitrary Code
Red Hat has issued a fix for Red Hat Enterprise Linux 4.



 Source Message Contents



[Original Message Not Available for Viewing]


Go to the Top of This SecurityTracker Archive Page





Home   |    View Topics   |    Search   |    Contact Us

This web site uses cookies for web analytics. Learn More

Copyright 2020, SecurityGlobal.net LLC