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

> An attacker can perform unlimited automated login attempts on Teltonika RTU9XX devices to crack user passwords and gain unauthorized access.

- **Severity:** High 7.1 (`CVSS:3.0/AC:L/AV:A/A:L/C:L/I:L/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mc55-hg68-v7m4

## What is CVE-2018-19879?

CVE-2018-19879 is a high-severity authentication bypass vulnerability in n/a, published on 28 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in /cgi-bin/luci on Teltonika RTU9XX (e.g., RUT950) R_31.04.89 before R_00.05.00.5 devices. The authentication functionality is not protected from automated tools used to make login attempts to the application. An anonymous attacker has the ability to make unlimited login attempts with an automated tool. This ability could lead to cracking a targeted user's password.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 1 product.


Products: Teltonika Rut950 Firmware.

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

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

## Is CVE-2018-19879 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19878](https://insights.sbomify.com/CVE-2018-19878/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19879 is a high-severity authentication bypass vulnerability in n/a, published on 28 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19879 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-19879/ (Markdown: https://insights.sbomify.com/CVE-2018-19879/index.md)
```

## Sources

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

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