# CVE-2017-1000002: Path traversal in n/a

> Attackers can exploit directory traversal and file extension bypasses in ATutor to execute arbitrary code or disclose sensitive information.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r5qj-vq8r-w5j5

## What is CVE-2017-1000002?

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

### Official description

ATutor versions 2.2.1 and earlier are vulnerable to a directory traversal and file extension check bypass in the Course component resulting in code execution. ATutor versions 2.2.1 and earlier are vulnerable to a directory traversal vulnerability in the Course Icon component resulting in information disclosure.

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

## Which versions are affected by CVE-2017-1000002?

It affects 1 product.


Products: Atutor Atutor.

## How do I fix CVE-2017-1000002?

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

## Is CVE-2017-1000002 being exploited?

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

Public exploit code:

- ATutor 2.2.1 Directory Traversal / Remote Code Execution (metasploit)

## Other vulnerabilities in n/a

- [CVE-2014-9753](https://insights.sbomify.com/CVE-2014-9753/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-16114](https://insights.sbomify.com/CVE-2019-16114/): Missing authorization in n/a (critical 9.8)
- [CVE-2017-1000003](https://insights.sbomify.com/CVE-2017-1000003/): Privilege escalation in n/a (critical 9.8)
- [CVE-2017-1000004](https://insights.sbomify.com/CVE-2017-1000004/): SQL injection in n/a (critical 9.8)
- [CVE-2016-2555](https://insights.sbomify.com/CVE-2016-2555/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000002 and fix it if it is affected.

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

## Sources

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

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