# CVE-2010-4835: Path traversal in n/a

> Authenticated attackers can read arbitrary files via directory traversal in the controller parameter of OneOrZero AIMS.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3w7x-45wj-hgjm

## What is CVE-2010-4835?

CVE-2010-4835 is a medium-severity path traversal vulnerability in n/a, published on 13 Sep 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in index.php in OneOrZero AIMS 2.6.0 Members Edition allows remote authenticated users to read arbitrary files via directory traversal sequences in the controller parameter in a show_report action.

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

## Which versions are affected by CVE-2010-4835?

It affects 1 product.


Products: Oneorzero Aims.

## How do I fix CVE-2010-4835?

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

## Is CVE-2010-4835 being exploited?

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

Public exploit code:

- OneOrZero AIms 2.6.0 Members Edition - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-4214](https://insights.sbomify.com/CVE-2011-4214/): Auth bypass in n/a (critical 10.0)
- [CVE-2011-4215](https://insights.sbomify.com/CVE-2011-4215/): SQL injection in n/a (high 7.5)
- [CVE-2010-4834](https://insights.sbomify.com/CVE-2010-4834/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4835 and fix it if it is affected.

What it is: CVE-2010-4835 is a medium-severity path traversal vulnerability in n/a, published on 13 Sep 2011. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-4835 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-2010-4835/ (Markdown: https://insights.sbomify.com/CVE-2010-4835/index.md)
```

## Sources

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

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