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

> Attackers can bypass authentication on Intelbras NPLUG wireless repeaters by setting a specific cookie, gaining unauthorized access to the web interface.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 10 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jq56-qcgv-3phx

## What is CVE-2018-12455?

CVE-2018-12455 is a high-severity authentication bypass vulnerability in n/a, published on 10 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Intelbras NPLUG 1.0.0.14 wireless repeater devices have a critical vulnerability that allows an attacker to authenticate in the web interface just by using "admin:" as the name of a cookie.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Intelbras Nplug Firmware.

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

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

## Is CVE-2018-12455 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-12455 exists.

Public exploit code:

- Intelbras NPLUG 1.0.0.14 - Authentication Bypass (nuclei): http/cves/2018/CVE-2018-12455.yaml

## Other vulnerabilities in n/a

- [CVE-2018-12456](https://insights.sbomify.com/CVE-2018-12456/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-17337](https://insights.sbomify.com/CVE-2018-17337/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12455 is a high-severity authentication bypass vulnerability in n/a, published on 10 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-12455 exists.

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-12455/ (Markdown: https://insights.sbomify.com/CVE-2018-12455/index.md)
```

## Sources

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

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