CVE-2005-1125: Race Condition

Published Apr 16, 2005
·
Updated

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 libsafedie function call is completed.

Affected Software

16 affected components
Avaya Libsafe=2.0.6
Avaya Libsafe=2.0.1
Avaya Libsafe=2.0.13
Avaya Libsafe=2.0.5
Avaya Libsafe=2.0.9
Avaya Libsafe=2.0.14
Avaya Libsafe=2.0.3
Avaya Libsafe=2.0.2
Avaya Libsafe=2.0.4
Avaya Libsafe=2.0.15
Avaya Libsafe=2.0.11
Avaya Libsafe=2.0.16
Avaya Libsafe=2.0.10
Avaya Libsafe=2.0.8
Avaya Libsafe=2.0.7
Avaya Libsafe=2.0.12

Event History

Apr 16, 2005
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2005-1125?

CVE-2005-1125 is considered to have a moderate severity level due to the potential for attackers to bypass security protections.

2

How do I fix CVE-2005-1125?

To fix CVE-2005-1125, upgrade to libsafe version 2.0.17 or later to eliminate the race condition vulnerability.

3

Which versions of libsafe are affected by CVE-2005-1125?

CVE-2005-1125 affects libsafe versions 2.0.1 through 2.0.16.

4

What causes the vulnerability in CVE-2005-1125?

The vulnerability in CVE-2005-1125 is caused by a race condition in libsafe when utilized in multi-threaded applications.

5

What is the main impact of CVE-2005-1125?

The main impact of CVE-2005-1125 is that it allows attackers to exploit other vulnerabilities bypassing libsafe protection.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203