# CVE-2014-4198: Auth bypass in n/a

> Attackers can bypass two-factor authentication in BS-Client Private Client by sending a crafted XML request, gaining unauthorized access to privileged functions.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 13 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j87h-xgjx-cfhm

## What is CVE-2014-4198?

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

### Official description

A Two-Factor Authentication Bypass Vulnerability exists in BS-Client Private Client 2.4 and 2.5 via an XML request that neglects the use of ADPswID and AD parameters, which could let a malicious user access privileged function.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2014-4198?

It affects 1 product.


Products: Bssys Rbs Bs-Client. Retail Client.

## How do I fix CVE-2014-4198?

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

## Is CVE-2014-4198 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-10398](https://insights.sbomify.com/CVE-2014-10398/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4198 and fix it if it is affected.

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

## Sources

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

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