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

> A buffer overflow in the Ruijie EG-2000 gateway allows attackers to bypass authentication and log in to any account without a password.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2024
- **Updated:** 12 Aug 2024
- **Also known as:** GHSA-v558-hc45-fcjv

## What is CVE-2019-16641?

CVE-2019-16641 is a high-severity memory corruption vulnerability in n/a, published on 16 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was found on the Ruijie EG-2000 series gateway. There is a buffer overflow in client.so. Consequently, an attacker can use login.php to login to any account, without providing its password. This affects EG-2000SE EG_RGOS 11.1(1)B1.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Ruijie Eg-2000se Firmware.

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

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

## Is CVE-2019-16641 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16639](https://insights.sbomify.com/CVE-2019-16639/): Command injection in n/a (critical 9.8)
- [CVE-2019-16638](https://insights.sbomify.com/CVE-2019-16638/): Information disclosure in n/a (high 7.5)
- [CVE-2019-16640](https://insights.sbomify.com/CVE-2019-16640/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16641 is a high-severity memory corruption vulnerability in n/a, published on 16 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-16641 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-2019-16641/ (Markdown: https://insights.sbomify.com/CVE-2019-16641/index.md)
```

## Sources

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

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