# CVE-2018-19878: Denial of service in n/a

> An attacker can exhaust device memory by repeatedly logging in without logging out, causing a denial of service on Teltonika RTU950 devices.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vwc5-x3cm-cc9v

## What is CVE-2018-19878?

CVE-2018-19878 is a medium-severity denial of service vulnerability in n/a, published on 19 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on Teltonika RTU950 R_31.04.89 devices. The application allows a user to login without limitation. For every successful login request, the application saves a session. A user can re-login without logging out, causing the application to store the session in memory. Exploitation of this vulnerability will increase memory use and consume free space.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Teltonika Rut950 Firmware.

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

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

## Is CVE-2018-19878 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19879](https://insights.sbomify.com/CVE-2018-19879/): Auth bypass in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19878 is a medium-severity denial of service vulnerability in n/a, published on 19 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-19878 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-19878/ (Markdown: https://insights.sbomify.com/CVE-2018-19878/index.md)
```

## Sources

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

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