# CVE-2016-8378: Hardcoded credentials in Lynxspring JENEsys BAS Bridge 1.1.8 and older

> Attackers can access stored credentials due to insufficient database safeguards in the JENEsys BAS Bridge, potentially leading to unauthorized system access.

- **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:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5hm4-vx3q-j68j

## What is CVE-2016-8378?

CVE-2016-8378 is a critical vulnerability in Lynxspring JENEsys BAS Bridge 1.1.8 and older, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Lynxspring JENEsys BAS Bridge versions 1.1.8 and older. The application's database lacks sufficient safeguards for protecting credentials.

Weakness: CWE-255

## Which versions are affected by CVE-2016-8378?

It affects 1 product.


Products: Lynxspring Jenesys Bas Bridge.

## How do I fix CVE-2016-8378?

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

## Is CVE-2016-8378 being exploited?

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

## Other vulnerabilities in Lynxspring JENEsys BAS Bridge 1.1.8 and older

- [CVE-2016-8369](https://insights.sbomify.com/CVE-2016-8369/): Cross-site request forgery in Lynxspring JENEsys BAS Bridge 1.1.8 and older (high 8.8)
- [CVE-2016-8361](https://insights.sbomify.com/CVE-2016-8361/): Hardcoded credentials in Lynxspring JENEsys BAS Bridge 1.1.8 and older (high 8.6)
- [CVE-2016-8357](https://insights.sbomify.com/CVE-2016-8357/): Missing authorization in Lynxspring JENEsys BAS Bridge 1.1.8 and older (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8378 and fix it if it is affected.

What it is: CVE-2016-8378 is a critical vulnerability in Lynxspring JENEsys BAS Bridge 1.1.8 and older, published on 13 Feb 2017. 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-2016-8378 in the wild and no public exploit code.

Affected product: Lynxspring JENEsys BAS Bridge 1.1.8 and older. 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-2016-8378/ (Markdown: https://insights.sbomify.com/CVE-2016-8378/index.md)
```

## Sources

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

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