glibc Buffer overwrite when using readdir_r

2013.08.13
Credit: Jan
Risk: High
Local: Yes
Remote: No
CWE: N/A


CVSS Base Score: 6.8/10
Impact Subscore: 6.4/10
Exploitability Subscore: 8.6/10
Exploit range: Remote
Attack complexity: Medium
Authentication: No required
Confidentiality impact: Partial
Integrity impact: Partial
Availability impact: Partial

An out-of buffer bounds write flaw was found in the way readdir_r() routine of glibc, the collection of GNU libc libraries, used to handle file system entry when its name was longer than NAME_MAX characters constant, defined by Linux kernel (readdir_r() used to put content of the directory read into application's allocated buffer, possibly [NTFS or CIFS filesystems for example] leading to application's buffer overwrite]. A remote-attacker could provide a specially-crafted NTFS or CIFS image that, when processed in an application using the readdir_r() functionality, would lead to that application crash or, potentially, arbitrary code execution with the privileges of the user running the application. This issue was found by Florian Weimer of Red Hat Product Security Team. Upstream bug report: [1] http://sourceware.org/bugzilla/show_bug.cgi?id=14699 Latest patch proposal: [2] http://sourceware.org/ml/libc-alpha/2013-05/msg00445.html References: [3] https://bugzilla.redhat.com/show_bug.cgi?id=995839 Thank you && Regards, Jan.

References:

https://bugzilla.redhat.com/show_bug.cgi?id=995839


Vote for this issue:
50%
50%


 

Thanks for you vote!


 

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.


(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2024, cxsecurity.com

 

Back to Top