# CVE-2002-0167: Command injection in n/a

> Attackers can cause crashes or execute arbitrary code by exploiting NetPBM weaknesses when Imlib loads trusted images.

- **Severity:** High 7.5 (`AV:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9723-3qmw-g98x

## What is CVE-2002-0167?

CVE-2002-0167 is a high-severity command injection vulnerability in n/a, published on 25 Jun 2002. 

### Official description

Imlib before 1.9.13 sometimes uses the NetPBM package to load trusted images, which could allow attackers to cause a denial of service (crash) and possibly execute arbitrary code via certain weaknesses of NetPBM.

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

It affects 1 product.


Products: Enlightenment Imlib.

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

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

## Is CVE-2002-0167 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1025](https://insights.sbomify.com/CVE-2004-1025/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1026](https://insights.sbomify.com/CVE-2004-1026/): Integer overflow in n/a (critical 10.0)
- [CVE-2002-0168](https://insights.sbomify.com/CVE-2002-0168/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0143](https://insights.sbomify.com/CVE-2002-0143/): Memory corruption in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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