How severe is CVE-2002-0175?

CVE-2002-0175 has a CVSS 2.0 base score of 4.6, rated medium severity.

Is CVE-2002-0175 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (37th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2002-0175?

CVE-2002-0175 primarily affects Avaya Libsafe. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2002-0175?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2002-0175 published?

CVE-2002-0175 was published on 2002-04-22 and last updated on 2026-06-16.

CVE-2002-0175

CVE-2002-0175 is a medium-severity vulnerability in Avaya Libsafe with a CVSS 2.0 base score of 4.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 4.6)
EPSS exploit prediction: 0% (37th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Avaya Libsafe
Published: 2002-04-22
Last modified: 2026-06-16

Description

libsafe 2.0-11 and earlier allows attackers to bypass protection against format string vulnerabilities via format strings that use the "'" and "I" characters, which are implemented in libc but not libsafe.

Frequently asked questions

What is CVE-2002-0175?: libsafe 2.0-11 and earlier allows attackers to bypass protection against format string vulnerabilities via format strings that use the "'" and "I" characters, which are implemented in libc but not libsafe.
How severe is CVE-2002-0175?: CVE-2002-0175 has a CVSS 2.0 base score of 4.6, rated medium severity.
Is CVE-2002-0175 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (37th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2002-0175?: CVE-2002-0175 primarily affects Avaya Libsafe. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2002-0175?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2002-0175 published?: CVE-2002-0175 was published on 2002-04-22 and last updated on 2026-06-16.

References

Affected products (7)

cpe:2.3:a:avaya:libsafe:1.3.4:*:*:*:*:*:*:*
cpe:2.3:a:avaya:libsafe:1.3.8:*:*:*:*:*:*:*
cpe:2.3:a:avaya:libsafe:2.0.2:*:*:*:*:*:*:*
cpe:2.3:a:avaya:libsafe:2.0.5:*:*:*:*:*:*:*
cpe:2.3:a:avaya:libsafe:2.0.9:*:*:*:*:*:*:*
cpe:2.3:a:avaya:libsafe:2.0.10:*:*:*:*:*:*:*
cpe:2.3:a:avaya:libsafe:2.0.11:*:*:*:*:*:*:*

More vulnerabilities in Avaya Libsafe

CVE-2005-1125 — Medium (CVSS 5.1): Race condition in libsafe 2.0.16 and earlier, when running in multi-threaded applications, allows attackers to bypass…
CVE-2002-0176 — Medium (CVSS 4.6): The printf wrappers in libsafe 2.0-11 and earlier do not properly handle argument indexing specifiers, which could…

All CVEs affecting Avaya Libsafe →