# CVE-2018-5465: Auth bypass in Hirschmann Automation and Control GmbH Classic Platform Switches

> Attackers can hijack web sessions on Hirschmann industrial switches via session fixation, potentially gaining unauthorized access to the management interface.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9xwx-w5gp-5r6x

## What is CVE-2018-5465?

CVE-2018-5465 is a high-severity authentication bypass vulnerability in Hirschmann Automation and Control GmbH Classic Platform Switches, published on 6 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Session Fixation issue was discovered in Belden Hirschmann RS, RSR, RSB, MACH100, MACH1000, MACH4000, MS, and OCTOPUS Classic Platform Switches. A session fixation vulnerability in the web interface has been identified, which may allow an attacker to hijack web sessions.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2018-5465?

It affects 134 products.


Products: Belden Hirschmann M1-8mm-Sc, Belden Hirschmann M1-8sfp, Belden Hirschmann M1-8sm-Sc, Belden Hirschmann M1-8tp-Rj45, Belden Hirschmann Mach102-24tp-F, Belden Hirschmann Mach102-24tp-Fr, Belden Hirschmann Mach102-8tp, Belden Hirschmann Mach102-8tp-F, Belden Hirschmann Mach102-8tp-Fr, Belden Hirschmann Mach102-8tp-R, Belden Hirschmann Mach104-16tx-Poep, Belden Hirschmann Mach104-16tx-Poep-L3p, Belden Hirschmann Mach104-16tx-Poep -E, Belden Hirschmann Mach104-16tx-Poep -E-L3p, Belden Hirschmann Mach104-16tx-Poep -R, Belden Hirschmann Mach104-16tx-Poep -R-L3p, Belden Hirschmann Mach104-16tx-Poep \+2x, Belden Hirschmann Mach104-16tx-Poep \+2x-L3p, Belden Hirschmann Mach104-16tx-Poep \+2x -E, Belden Hirschmann Mach104-16tx-Poep \+2x -E-L3p and 114 more.

## How do I fix CVE-2018-5465?

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

## Is CVE-2018-5465 being exploited?

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

## Other vulnerabilities in Hirschmann Automation and Control GmbH Classic Platform Switches

- [CVE-2018-5469](https://insights.sbomify.com/CVE-2018-5469/): Auth bypass in Hirschmann Automation and Control GmbH Classic Platform Switches (critical 9.8)
- [CVE-2018-5461](https://insights.sbomify.com/CVE-2018-5461/): Weak cryptography in Hirschmann Automation and Control GmbH Classic Platform Switches (medium 6.5)
- [CVE-2018-5467](https://insights.sbomify.com/CVE-2018-5467/): Information disclosure in Hirschmann Automation and Control GmbH Classic Platform Switches (medium 6.5)
- [CVE-2018-5471](https://insights.sbomify.com/CVE-2018-5471/): Information disclosure in Hirschmann Automation and Control GmbH Classic Platform Switches (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5465 and fix it if it is affected.

What it is: CVE-2018-5465 is a high-severity authentication bypass vulnerability in Hirschmann Automation and Control GmbH Classic Platform Switches, published on 6 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-5465 in the wild and no public exploit code.

Affected product: Hirschmann Automation and Control GmbH Classic Platform Switches. 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-2018-5465/ (Markdown: https://insights.sbomify.com/CVE-2018-5465/index.md)
```

## Sources

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

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