# CVE-2020-11542: Auth bypass in n/a

> Attackers can bypass authentication on Infinias eIDC32 devices by manipulating client-side key interpretation in the web interface.

- **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:** 4 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-86q8-rg63-hvmr

## What is CVE-2020-11542?

CVE-2020-11542 is a critical authentication bypass vulnerability in n/a, published on 4 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

3xLOGIC Infinias eIDC32 2.213 devices with Web 1.107 allow Authentication Bypass via CMD.HTM?CMD= because authentication depends on the client side's interpretation of the <KEY>MYKEY</KEY> substring.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2020-11542?

It affects 2 products.


Products: 3xlogic Infinias Eidc32 Firmware, 3xlogic Infinias Eidc32 Web.

## How do I fix CVE-2020-11542?

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

## Is CVE-2020-11542 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12681](https://insights.sbomify.com/CVE-2020-12681/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11542 and fix it if it is affected.

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

## Sources

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

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