# CVE-2004-2687: Missing authorization in n/a

> Remote attackers can execute arbitrary commands on distcc servers if access restrictions are not configured, leading to full system compromise.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Sep 2007
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2004-2687, GHSA-88vv-hvrc-733q

## What is CVE-2004-2687?

CVE-2004-2687 is a critical missing authorization vulnerability in Apple Xcode, published on 23 Sep 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

distcc 2.x, as used in XCode 1.5 and others, when not configured to restrict access to the server port, allows remote attackers to execute arbitrary commands via compilation jobs, which are executed by the server without authorization checks.

Weakness: CWE-16

## Which versions are affected by CVE-2004-2687?

It affects 2 products.


Products: Apple Xcode, Samba Samba.

## How do I fix CVE-2004-2687?

Change a configuration setting.

## Is CVE-2004-2687 being exploited?

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

Public exploit code:

- https://github.com/h3x0v3rl0rd/distccd_rce_CVE-2004-2687 (github_poc): https://github.com/h3x0v3rl0rd/distccd_rce_CVE-2004-2687
- CVE-2004-2687 DistCC Daemon Command Execution (github_poc): https://github.com/k4miyo/CVE-2004-2687
- CVE-2004-2687 (Distcc 3.2.1) exploitation, methodology & remediation — Metasploitable2 lab  (github_poc): https://github.com/germarr93/CyberSecurity-Pentest-Lab
- DistCC Daemon - Command Execution (Metasploit) (exploitdb)
- DistCC Daemon Command Execution (metasploit)
- Ushbu videoda Metasploitable 2 tizimidagi distccd servisidagi zaiflikdan foydalanib, Kali Linux orqali remote shell olish ko‘rsatib beriladi. (github_poc): https://github.com/nulltrace1336/Metasploitable-2-Distcc-Exploit-via-Kali-Linux-CVE-2004-2687

## Other vulnerabilities in Apple Xcode

- [CVE-2025-48384](https://insights.sbomify.com/CVE-2025-48384/): Git Link Following (high 8.1, exploited in the wild)
- [CVE-2014-9390](https://insights.sbomify.com/CVE-2014-9390/): JGit Improper Input Validation vulnerability (critical 9.8)
- [CVE-2019-14379](https://insights.sbomify.com/CVE-2019-14379/): Deserialization of untrusted data in FasterXML jackson-databind (critical 9.8)
- [CVE-2018-4164](https://insights.sbomify.com/CVE-2018-4164/): An issue was discovered in certain Apple products. (critical 9.8)
- [CVE-2016-0746](https://insights.sbomify.com/CVE-2016-0746/): Use after free in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2687 and fix it if it is affected.

What it is: CVE-2004-2687 is a critical missing authorization vulnerability in Apple Xcode, published on 23 Sep 2007. 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-2004-2687 exists.

Affected product: Apple Xcode. 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-2004-2687/ (Markdown: https://insights.sbomify.com/CVE-2004-2687/index.md)
```

## Sources

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

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