# CVE-2002-0176: Other in n/a

> Attackers can bypass libsafe protections in printf wrappers to execute arbitrary code via unverified arguments.

- **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:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-38pf-hw2h-2w5q

## What is CVE-2002-0176?

CVE-2002-0176 is a medium-severity vulnerability in n/a, published on 25 Jun 2002. 

### Official description

The printf wrappers in libsafe 2.0-11 and earlier do not properly handle argument indexing specifiers, which could allow attackers to exploit certain function calls through arguments that are not verified by libsafe.

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

It affects 1 product.


Products: Avaya Libsafe.

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

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

## Is CVE-2002-0176 being exploited?

There is no known exploitation of CVE-2002-0176 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-0175](https://insights.sbomify.com/CVE-2002-0175/): Security feature bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0176 is a medium-severity vulnerability in n/a, published on 25 Jun 2002. 
Exploitation: There is no known exploitation of CVE-2002-0176 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-0176/ (Markdown: https://insights.sbomify.com/CVE-2002-0176/index.md)
```

## Sources

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

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