# CVE-2005-0158: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via format string vulnerabilities in bidwatcher responses.

- **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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-687-1, GHSA-fg5x-5cvc-6wxg

## What is CVE-2005-0158?

CVE-2005-0158 is a high-severity memory corruption vulnerability in n/a, published on 18 Feb 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Format string vulnerability in bidwatcher before 1.3.17 allows remote malicious web servers from eBay, or a spoofed eBay server, to cause a denial of service and possibly execute arbitrary code via certain responses.

## Which versions are affected by CVE-2005-0158?

It affects 1 product.


Products: Bidwatcher Bidwatcher.

## How do I fix CVE-2005-0158?

Upgrade to a fixed version.

## Is CVE-2005-0158 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0158 and fix it if it is affected.

What it is: CVE-2005-0158 is a high-severity memory corruption vulnerability in n/a, published on 18 Feb 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-0158 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-2005-0158/ (Markdown: https://insights.sbomify.com/CVE-2005-0158/index.md)
```

## Sources

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

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