# CVE-2018-6020: Auth bypass in n/a

> Attackers can bypass authentication on Silex and GE IoT devices to modify system settings via unverified POST requests.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-vg3g-97mm-4p4w

## What is CVE-2018-6020?

CVE-2018-6020 is a medium-severity authentication bypass vulnerability in n/a, published on 9 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Silex SX-500 all versions and GE MobileLink(GEH-500) version 1.54 and prior, authentication is not verified when making certain POST requests, which may allow attackers to modify system settings.

Weakness: CWE-287 (Improper Authentication)

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

It affects 4 products.


Products: Silextechnology Geh-500 Firmware, Silextechnology Geh-Sd-320an Firmware, Silextechnology Sd-320an Firmware, Silextechnology Sx-500 Firmware.

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

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

## Is CVE-2018-6020 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6020 is a medium-severity authentication bypass vulnerability in n/a, published on 9 May 2018. 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-2018-6020 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-2018-6020/ (Markdown: https://insights.sbomify.com/CVE-2018-6020/index.md)
```

## Sources

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

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