# CVE-2019-5616: CircuitWerkes Sicon-8 Client-Side Authentication Read-Only Bypass

> Attackers can bypass client-side JavaScript authentication to access read-only functions on the Sicon-8 electrical management device.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-q93g-7855-pfx5

## What is CVE-2019-5616?

CVE-2019-5616 is a medium-severity authentication bypass vulnerability in n/a, published on 15 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CircuitWerkes Sicon-8, a hardware device used for managing electrical devices, ships with a web-based front-end controller and implements an authentication mechanism in JavaScript that is run in the context of a user's web browser.

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

It affects 1 product.


Products: Broadcastboxes Scion-8 Firmware.

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

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

## Is CVE-2019-5616 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5616 is a medium-severity authentication bypass vulnerability in n/a, published on 15 Mar 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-5616 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-5616/ (Markdown: https://insights.sbomify.com/CVE-2019-5616/index.md)
```

## Sources

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

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