# CVE-2016-10399: Path traversal in n/a

> Unauthenticated remote attackers can read sensitive system files via Local File Inclusion in Sendio email security appliances.

- **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:** 27 Jul 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8mhf-4c94-v897

## What is CVE-2016-10399?

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

### Official description

Sendio versions before 8.2.1 were affected by a Local File Inclusion vulnerability that allowed an unauthenticated, remote attacker to read potentially sensitive system files via a specially crafted URL.

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory)

## Which versions are affected by CVE-2016-10399?

It affects 1 product.


Products: Sendio Sendio.

## How do I fix CVE-2016-10399?

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

## Is CVE-2016-10399 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-0999](https://insights.sbomify.com/CVE-2014-0999/): Information disclosure in n/a (medium 5.0)
- [CVE-2014-8391](https://insights.sbomify.com/CVE-2014-8391/): Information disclosure in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10399 and fix it if it is affected.

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

## Sources

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

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