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

> Remote attackers on the same network can change the admin password without authentication due to missing password verification in the web interface.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 20 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qcj2-5q38-5458

## What is CVE-2018-18871?

CVE-2018-18871 is a critical authentication bypass vulnerability in n/a, published on 20 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing password verification in the web interface on Gigaset Maxwell Basic VoIP phones with firmware 2.22.7 would allow a remote attacker (in the same network as the device) to change the admin password without authentication (and without knowing the original password).

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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

It affects 1 product.


Products: Gigasetpro Maxwell Basic Firmware.

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

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

## Is CVE-2018-18871 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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