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

> Remote attackers can bypass authentication in RSA NetWitness and Security Analytics by leveraging valid account names when Kerberos PAM is enabled.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9jwq-fvh8-f7jx

## What is CVE-2014-0643?

CVE-2014-0643 is a high-severity authentication bypass vulnerability in n/a, published on 16 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EMC RSA NetWitness before 9.8.5.19 and RSA Security Analytics before 10.2.4 and 10.3.x before 10.3.2, when Kerberos PAM is enabled, do not require a password, which allows remote attackers to bypass authentication by leveraging knowledge of a valid account name.

Weakness: CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Emc Rsa Netwitness, Emc Rsa Security Analytics.

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

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

## Is CVE-2014-0643 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11061](https://insights.sbomify.com/CVE-2018-11061/): Code injection in RSA NetWitness (critical 9.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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