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

> Remote attackers can cause denial of service or execute arbitrary code via buffer overflows in TrackerCam.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 19 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p3v5-qwwv-25vf

## What is CVE-2005-0478?

CVE-2005-0478 is a medium-severity memory corruption vulnerability in n/a, published on 19 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple buffer overflows in TrackerCam 5.12 and earlier allow remote attackers to cause a denial of service and possibly execute arbitrary code via (1) an HTTP request with a long User-Agent header or (2) a long argument to an arbitrary PHP script.

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

It affects 1 product.


Products: Trackercam Trackercam.

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

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

## Is CVE-2005-0478 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0478 exists.

Public exploit code:

- TrackerCam PHP Argument Buffer Overflow (metasploit)
- TrackerCam - PHP Argument Buffer Overflow (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-0479](https://insights.sbomify.com/CVE-2005-0479/): Path traversal in n/a (medium 5.0)
- [CVE-2005-0481](https://insights.sbomify.com/CVE-2005-0481/): Information disclosure in n/a (medium 5.0)
- [CVE-2005-0482](https://insights.sbomify.com/CVE-2005-0482/): Denial of service in n/a (medium 5.0)
- [CVE-2005-0480](https://insights.sbomify.com/CVE-2005-0480/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0478 is a medium-severity memory corruption vulnerability in n/a, published on 19 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-0478 exists.

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-0478/ (Markdown: https://insights.sbomify.com/CVE-2005-0478/index.md)
```

## Sources

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

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