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

> Attackers can bypass authentication and execute SQL queries by intercepting unencrypted client traffic due to disabled TLS in default configuration.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 25 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pc36-887c-pv53

## What is CVE-2019-19127?

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

### Official description

An authentication bypass vulnerability is present in the standalone SITS:Vision 9.7.0 component of Tribal SITS in its default configuration, related to unencrypted communications sent by the client each time it is launched. This occurs because the Uniface TLS Driver is not enabled by default. This vulnerability allows attackers to gain access to credentials or execute arbitrary SQL queries on the SITS backend as long as they have access to the client executable or can intercept traffic from a user who does.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Tribalgroup Sits\.

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

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

## Is CVE-2019-19127 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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