# CVE-2016-5788: Auth bypass in n/a

> Remote attackers can obtain privileged access to GE Bently Nevada 3500 devices due to open ports, requiring firmware upgrades to mitigate.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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:** 25 Nov 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m82x-rphm-xj9w

## What is CVE-2016-5788?

CVE-2016-5788 is a critical authentication bypass vulnerability in n/a, published on 25 Nov 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

General Electric (GE) Bently Nevada 3500/22M USB with firmware before 5.0 and Bently Nevada 3500/22M Serial have open ports, which makes it easier for remote attackers to obtain privileged access via unspecified vectors.

Weakness: CWE-285 (Improper Authorization), CWE-254

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

It affects 2 products.


Products: Ge Bently Nevada 3500\/22m Serial Firmware, Ge Bently Nevada 3500\/22m Usb Firmware.

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

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

## Is CVE-2016-5788 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-5788 is a critical authentication bypass vulnerability in n/a, published on 25 Nov 2016. 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-5788 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-5788/ (Markdown: https://insights.sbomify.com/CVE-2016-5788/index.md)
```

## Sources

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

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