[原文]Race condition in libsafe 2.0.16 and earlier, when running in multi-threaded applications, allows attackers to bypass libsafe protection and exploit other vulnerabilities before the _libsafe_die function call is completed.
Libsafe contains a flaw that may allow a malicious user to bypass libsafe security mechanisms in a multi-threaded application linked against the vulnerable library. The issue is due to a race condition when processing simultaneous attacks in separated threads, resulting in a loss of integrity.
Currently, there are no known upgrades, patches, or workarounds available to correct this issue.
Libsafe will normally kill an application when certain types of memory corruption are detected, preventing exploitation of some buffer overflow and format string vulnerabilities. A weakness has been reported that may allow Libsafe security failsafe mechanisms to be bypassed.
This vulnerability is due to a race condition that may be exposed when Libsafe is used with multi-threaded applications. The result is that Libsafe security features may be bypassed and an attack that would ordinarily be prevented may succeed. It should be noted that this is an implementation error in Libsafe that does not present a security risk unless there is a memory corruption vulnerability in a multi-threaded application on an affected computer.
This issue was reported in Libsafe 2.0-16. Other versions may also be affected.
A proof-of-concept was provided to demonstrate the issue. The proof-of-concept may need to be executed multiple times to successfully exploit the issue.
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or are aware of more recent information, please mail us at: email@example.com <mailto:firstname.lastname@example.org>.