# CVE-2002-0175: Security feature bypass in n/a

> Attackers can bypass libsafe format string protections using specific characters, potentially enabling code execution in applications relying on this library.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3ccv-38v3-xjvw

## What is CVE-2002-0175?

CVE-2002-0175 is a medium-severity vulnerability in n/a, published on 25 Jun 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2002-0175?

It affects 1 product.


Products: Avaya Libsafe.

## How do I fix CVE-2002-0175?

No fix has been published for CVE-2002-0175 yet. Limit exposure of the affected software until one is available.

## Is CVE-2002-0175 being exploited?

There is no known exploitation of CVE-2002-0175 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2005-1125](https://insights.sbomify.com/CVE-2005-1125/): Race condition in n/a (medium 5.1)
- [CVE-2002-0176](https://insights.sbomify.com/CVE-2002-0176/): Other in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0175 and fix it if it is affected.

What it is: CVE-2002-0175 is a medium-severity vulnerability in n/a, published on 25 Jun 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0175 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2002-0175/ (Markdown: https://insights.sbomify.com/CVE-2002-0175/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2002-0175
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2002-0175
- OSV: https://osv.dev/vulnerability/CVE-2002-0175

---
From sbomify Insights: https://insights.sbomify.com/CVE-2002-0175/
Summaries are generated and may contain mistakes; the official description above is the record.