# CVE-2016-5804: Weak cryptography in n/a

> Weak encryption in Moxa MGate gateways allows remote attackers to bypass authentication via brute-force guessing of parameter values.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 15 Jul 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5cr2-3qp3-5h49

## What is CVE-2016-5804?

CVE-2016-5804 is a critical vulnerability in n/a, published on 15 Jul 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Moxa MGate MB3180 before 1.8, MGate MB3280 before 2.7, MGate MB3480 before 2.6, MGate MB3170 before 2.5, and MGate MB3270 before 2.7 use weak encryption, which allows remote attackers to bypass authentication via a brute-force series of guesses for a parameter value.

Weakness: CWE-326 (Inadequate Encryption Strength)

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

It affects 5 products.


Products: Moxa Mgate Mb3170 Firmware, Moxa Mgate Mb3180 Firmware, Moxa Mgate Mb3270 Firmware, Moxa Mgate Mb3280 Firmware, Moxa Mgate Mb3480 Firmware.

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

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

## Is CVE-2016-5804 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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