# CVE-2019-20046: Auth bypass in n/a

> Attackers can bypass authentication to read sensitive data or execute arbitrary code on HUSKY RTU devices.

- **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 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7g5r-3c9x-4h45

## What is CVE-2019-20046?

CVE-2019-20046 is a critical authentication bypass vulnerability in n/a, published on 14 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Synergy Systems & Solutions PLC & RTU system has a vulnerability in HUSKY RTU 6049-E70 firmware versions 5.0 and prior. The affected product does not require adequate authentication, which may allow an attacker to read sensitive information or execute arbitrary code. This is a different issue than CVE-2019-16879 and CVE-2019-20045.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: S3india Husky Rtu 6049-E70 Firmware.

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

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

## Is CVE-2019-20046 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20045](https://insights.sbomify.com/CVE-2019-20045/): Denial of service in n/a (high 7.5)
- [CVE-2020-7802](https://insights.sbomify.com/CVE-2020-7802/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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