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

> Attackers can bypass firewall protections on Belden Hirschmann Tofino Xenon appliances to access protected assets via crafted OPC traffic.

- **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:** 20 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g5fp-55mr-fxj5

## What is CVE-2017-11402?

CVE-2017-11402 is a critical vulnerability in n/a, published on 20 Nov 2017. An attacker can exploit it over the internet without logging in, 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. Design flaws in OPC classic and in custom netfilter modules allow an attacker to remotely activate rules on the firewall and to connect to any TCP port of a protected asset, thus bypassing the firewall. The attack methodology is a crafted OPC dynamic port shift.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Belden Tofino Xenon Security Appliance Firmware.

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

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

## Is CVE-2017-11402 being exploited?

There is no known exploitation of CVE-2017-11402 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-11400](https://insights.sbomify.com/CVE-2017-11400/): Security feature bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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