CVE-2005-1125 describes a race condition in libsafe 2.0.16 and earlier, specifically impacting multi-threaded applications. This flaw allows attackers to bypass libsafe's protective measures, potentially enabling the exploitation of other vulnerabilities before libsafe can fully execute its error handling. With a CVSS score of 5.1 and a FAUCET Risk Score of 83/100, this vulnerability has a network attack vector and high attack complexity, leading to potential partial confidentiality, integrity, and availability impacts. While not listed on CISA's KEV catalog and with no active exploitation observed, an ExploitDB entry (EDB-25429) exists, indicating public exploit code availability, though community discussion and media coverage are minimal.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
2.0.1CPE matchmatch criteria | cpe:2.3:a:avaya:libsafe:2.0.1:*:*:*:*:*:*:* | ||
2.0.2CPE matchmatch criteria | cpe:2.3:a:avaya:libsafe:2.0.2:*:*:*:*:*:*:* | ||
2.0.3CPE matchmatch criteria | cpe:2.3:a:avaya:libsafe:2.0.3:*:*:*:*:*:*:* | ||
2.0.4CPE matchmatch criteria | cpe:2.3:a:avaya:libsafe:2.0.4:*:*:*:*:*:*:* | ||
2.0.5CPE matchmatch criteria | cpe:2.3:a:avaya:libsafe:2.0.5:*:*:*:*:*:*:* |
CVSS version used by this source: 2.0
AV:N/AC:H/Au:N/C:P/I:P/A:P
No social media mentions found for this CVE.
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.0 Bluesky, 0.0 Mastodon, and 0.2 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.0 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Remediation records are not available for this CVE.