# CVE-2005-4659: Privilege escalation in n/a

> Local attackers can escalate privileges by exploiting world-readable backup keys to restore malicious configurations via the system restore utility.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/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:** 16 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9m7h-2ggv-4q9j

## What is CVE-2005-4659?

CVE-2005-4659 is a low-severity vulnerability in n/a, published on 16 Jan 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IPCop (aka IPCop Firewall) before 1.4.10 has world-readable permissions for the backup.key file, which might allow local users to overwrite system configuration files and gain privileges by creating a malicious encrypted backup archive owned by "nobody", then executing ipcoprscfg to restore from this backup.

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

It affects 1 product.


Products: Ipcop Ipcop.

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

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

## Is CVE-2005-4659 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1210](https://insights.sbomify.com/CVE-2004-1210/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2013-7418](https://insights.sbomify.com/CVE-2013-7418/): Command injection in n/a (medium 6.5)
- [CVE-2013-7417](https://insights.sbomify.com/CVE-2013-7417/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2005-4660](https://insights.sbomify.com/CVE-2005-4660/): Race condition in n/a (low 1.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-4659 is a low-severity vulnerability in n/a, published on 16 Jan 2006. 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-4659 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-4659/ (Markdown: https://insights.sbomify.com/CVE-2005-4659/index.md)
```

## Sources

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

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