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

> An attacker can access files in an unspecified directory due to improper access restrictions in TRITON AP-EMAIL.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 6 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w7j8-5xhg-jwrw

## What is CVE-2017-11177?

CVE-2017-11177 is a high-severity path traversal vulnerability in n/a, published on 6 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TRITON AP-EMAIL 8.2 before 8.2 IB does not properly restrict file access in an unspecified directory.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Websense Triton Ap Email.

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

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

## Is CVE-2017-11177 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2763](https://insights.sbomify.com/CVE-2015-2763/): Other in n/a (critical 10.0)
- [CVE-2015-2767](https://insights.sbomify.com/CVE-2015-2767/): Unspecified vulnerability in Websense TRITON AP-EMAIL before 8.0.0 has unknown impact and attack vectors, related to "Autocomplete Enabled." (critical 10.0)
- [CVE-2015-2769](https://insights.sbomify.com/CVE-2015-2769/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2015-2766](https://insights.sbomify.com/CVE-2015-2766/): Auth bypass in n/a (medium 5.0)
- [CVE-2015-2771](https://insights.sbomify.com/CVE-2015-2771/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11177 is a high-severity path traversal vulnerability in n/a, published on 6 Nov 2017. 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-2017-11177 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-2017-11177/ (Markdown: https://insights.sbomify.com/CVE-2017-11177/index.md)
```

## Sources

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

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