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

> Remote attackers can obtain cleartext credentials from Moxa ioLogik devices and configuration utility due to improper encryption.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xqqm-hh5r-8934

## What is CVE-2016-2282?

CVE-2016-2282 is a medium-severity vulnerability in n/a, published on 4 Mar 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Moxa ioLogik E2200 devices before 3.12 and ioAdmin Configuration Utility before 3.18 do not properly encrypt credentials, which makes it easier for remote attackers to obtain the associated cleartext via unspecified vectors.

Weakness: CWE-255

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

It affects 2 products.


Products: Moxa Ioadmin Firmware, Moxa Iologik Firmware.

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

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

## Is CVE-2016-2282 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-2283](https://insights.sbomify.com/CVE-2016-2283/): Weak cryptography in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-2282 is a medium-severity vulnerability in n/a, published on 4 Mar 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-2282 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-2282/ (Markdown: https://insights.sbomify.com/CVE-2016-2282/index.md)
```

## Sources

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

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