# CVE-2019-16879: Missing authorization in n/a

> Attackers can access TELNET without authentication to modify configuration or perform malicious activities on the HUSKY RTU.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 14 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xh47-8887-mw3h

## What is CVE-2019-16879?

CVE-2019-16879 is a critical missing authorization vulnerability in n/a, published on 14 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Synergy Systems & Solutions (SSS) HUSKY RTU 6049-E70, with firmware Versions 5.0 and prior, has a Missing Authentication for Critical Function (CWE-306) vulnerability. The affected product does not require authentication for TELNET access, which may allow an attacker to change configuration or perform other malicious activities.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Mysyngeryss Husky Rtu 6049-E70 Firmware.

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

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

## Is CVE-2019-16879 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-7800](https://insights.sbomify.com/CVE-2020-7800/): Denial of service in n/a (high 8.2)
- [CVE-2020-7801](https://insights.sbomify.com/CVE-2020-7801/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16879 is a critical missing authorization vulnerability in n/a, published on 14 Apr 2020. 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-16879 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-16879/ (Markdown: https://insights.sbomify.com/CVE-2019-16879/index.md)
```

## Sources

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

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