# CVE-2017-11400: Security feature bypass in n/a

> Local attackers can bypass firmware signature checks to install malicious kernel and file system updates on Belden Hirschmann Tofino Xenon appliances.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mrc4-5458-65m9

## What is CVE-2017-11400?

CVE-2017-11400 is a medium-severity vulnerability in n/a, published on 20 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue has been discovered on the Belden Hirschmann Tofino Xenon Security Appliance before 03.2.00. An incomplete firmware signature allows a local attacker to upgrade the equipment (kernel, file system) with unsigned, attacker-controlled, data. This occurs because the appliance_config file is signed but the .tar.sec file is unsigned.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 1 product.


Products: Belden Tofino Xenon Security Appliance Firmware.

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

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

## Is CVE-2017-11400 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11401](https://insights.sbomify.com/CVE-2017-11401/): Security feature bypass in n/a (critical 9.8)
- [CVE-2017-11402](https://insights.sbomify.com/CVE-2017-11402/): Security feature bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11400 is a medium-severity vulnerability in n/a, published on 20 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11400 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-11400/ (Markdown: https://insights.sbomify.com/CVE-2017-11400/index.md)
```

## Sources

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

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