# CVE-2012-1617: Path traversal in n/a

> Remote attackers can read and write arbitrary files via directory traversal in OSClass, potentially leading to code execution.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2j7m-x4gh-v3m8

## What is CVE-2012-1617?

CVE-2012-1617 is a medium-severity path traversal vulnerability in n/a, published on 26 Sep 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in combine.php in OSClass before 2.3.6 allows remote attackers to read and write arbitrary files via a .. (dot dot) in the type parameter.  NOTE: this vulnerability can be leveraged to upload arbitrary files.

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

## Which versions are affected by CVE-2012-1617?

It affects 1 product.


Products: Juan Ramon Osclass.

## How do I fix CVE-2012-1617?

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

## Is CVE-2012-1617 being exploited?

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

Public exploit code:

- OSClass 2.3.x - Directory Traversal / Arbitrary File Upload (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-0974](https://insights.sbomify.com/CVE-2012-0974/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1617 and fix it if it is affected.

What it is: CVE-2012-1617 is a medium-severity path traversal vulnerability in n/a, published on 26 Sep 2012. 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-2012-1617 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-2012-1617/ (Markdown: https://insights.sbomify.com/CVE-2012-1617/index.md)
```

## Sources

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

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