# CVE-2019-8985: Memory corruption in n/a

> Unauthenticated attackers can trigger a stack-based buffer overflow via a long HTTP Authorization header, leading to remote code execution or device restart.

- **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:** 21 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-842g-r5mc-p7w4

## What is CVE-2019-8985?

CVE-2019-8985 is a critical memory corruption vulnerability in n/a, published on 21 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Netis WF2411 with firmware 2.1.36123 and other Netis WF2xxx devices (possibly WF2411 through WF2880), there is a stack-based buffer overflow that does not require authentication. This can cause denial of service (device restart) or remote code execution. This vulnerability can be triggered by a GET request with a long HTTP "Authorization: Basic" header that is mishandled by user_auth->user_ok in /bin/boa.

Weakness: CWE-787 (Out-of-bounds Write), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2019-8985?

It affects 2 products.


Products: Netis-Systems Wf2411 Firmware, Netis-Systems Wf2880 Firmware.

## How do I fix CVE-2019-8985?

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

## Is CVE-2019-8985 being exploited?

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

Public exploit code:

- CVE–2019–8985 Netis WF2411 RCE (github_poc): https://github.com/Squirre17/CVE-2019-8985

## Other vulnerabilities in n/a

- [CVE-2021-26747](https://insights.sbomify.com/CVE-2021-26747/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-8985 and fix it if it is affected.

What it is: CVE-2019-8985 is a critical memory corruption vulnerability in n/a, published on 21 Feb 2019. 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-2019-8985 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-2019-8985/ (Markdown: https://insights.sbomify.com/CVE-2019-8985/index.md)
```

## Sources

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

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