# CVE-2008-3150: Path traversal in n/a

> Remote attackers can exploit a directory traversal flaw in Neutrino Atomic Edition to read, modify files, and execute arbitrary code.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** No
- **Published:** 11 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x6rv-c4jg-frh2

## What is CVE-2008-3150?

CVE-2008-3150 is a critical path traversal vulnerability in n/a, published on 11 Jul 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in index.php in Neutrino Atomic Edition 0.8.4 allows remote attackers to read and modify files, as demonstrated by manipulating data/sess.php in (1) usb and (2) del_pag actions.  NOTE: this can be leveraged for code execution by performing an upload that bypasses the intended access restrictions that were implemented in sess.php.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2008-3150?

It affects 1 product.


Products: Neutrino-Cms Atomic Edition.

## How do I fix CVE-2008-3150?

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

## Is CVE-2008-3150 being exploited?

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

Public exploit code:

- QNX Neutrino 0.8.4 Atomic Edition - Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3150 and fix it if it is affected.

What it is: CVE-2008-3150 is a critical path traversal vulnerability in n/a, published on 11 Jul 2008. 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-2008-3150 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-2008-3150/ (Markdown: https://insights.sbomify.com/CVE-2008-3150/index.md)
```

## Sources

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

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