# CVE-2006-0636: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in eyeOS by manipulating session variables due to improper session initialization checks.

- **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:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7xx2-j9qr-rjp6

## What is CVE-2006-0636?

CVE-2006-0636 is a high-severity code injection vulnerability in n/a, published on 10 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

desktop.php in eyeOS 0.8.9 and earlier tests for the existence of the _SESSION variable before calling the session_start function, which allows remote attackers to execute arbitrary PHP code and possibly conduct other attacks by modifying critical assumed-immutable variables, as demonstrated using PHP code in the _SESSION[apps][eyeOptions.eyeapp][wrapup] variable.

## Which versions are affected by CVE-2006-0636?

It affects 1 product.


Products: Eyeos Project Eyeos.

## How do I fix CVE-2006-0636?

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

## Is CVE-2006-0636 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3414](https://insights.sbomify.com/CVE-2005-3414/): Information disclosure in n/a (high 7.5)
- [CVE-2007-4609](https://insights.sbomify.com/CVE-2007-4609/): Auth bypass in n/a (medium 6.4)
- [CVE-2006-5071](https://insights.sbomify.com/CVE-2006-5071/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2005-3413](https://insights.sbomify.com/CVE-2005-3413/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0636 and fix it if it is affected.

What it is: CVE-2006-0636 is a high-severity code injection vulnerability in n/a, published on 10 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0636 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-2006-0636/ (Markdown: https://insights.sbomify.com/CVE-2006-0636/index.md)
```

## Sources

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

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