# CVE-2005-1880: Path traversal in n/a

> Local attackers can overwrite arbitrary files via symlink attacks on temporary files created by wget in everybuddy.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v4r8-qwq6-39xh

## What is CVE-2005-1880?

CVE-2005-1880 is a medium-severity path traversal vulnerability in n/a, published on 7 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

everybuddy 0.4.3 and earlier allows local users to overwrite arbitrary files via a symlink attack on a temporary file created by a system call to wget.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Everybuddy Everybuddy.

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

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

## Is CVE-2005-1880 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1880 is a medium-severity path traversal vulnerability in n/a, published on 7 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-1880 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-1880/ (Markdown: https://insights.sbomify.com/CVE-2005-1880/index.md)
```

## Sources

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

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