# CVE-2014-0627: Weak cryptography in n/a

> Remote attackers can force weak cipher suite selection in EMC RSA BSAFE SSL-J, compromising encryption security.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 18 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-966j-2594-mwh4

## What is CVE-2014-0627?

CVE-2014-0627 is a medium-severity vulnerability in n/a, published on 18 Feb 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SSLEngine API implementation in EMC RSA BSAFE SSL-J 5.x before 5.1.3 and 6.x before 6.0.2 allows remote attackers to trigger the selection of a weak cipher suite by using the wrap method during a certain incomplete-handshake state.

Weakness: CWE-310

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

It affects 2 products.


Products: Dell Bsafe Ssl-J, Emc Rsa Bsafe Ssl-J.

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

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

## Is CVE-2014-0627 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-29171](https://insights.sbomify.com/CVE-2024-29171/): Security feature bypass in Dell BSAFE SSL-J (medium 5.9)
- [CVE-2024-29172](https://insights.sbomify.com/CVE-2024-29172/): Denial of service in Dell BSAFE SSL-J (medium 5.9)
- [CVE-2022-24409](https://insights.sbomify.com/CVE-2022-24409/): Information disclosure in Dell BSAFE SSL-J (medium 5.9)
- [CVE-2018-11069](https://insights.sbomify.com/CVE-2018-11069/): Weak cryptography in RSA BSAFE SSL-J (medium 5.9)
- [CVE-2014-0625](https://insights.sbomify.com/CVE-2014-0625/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0627 is a medium-severity vulnerability in n/a, published on 18 Feb 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-0627 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-0627/ (Markdown: https://insights.sbomify.com/CVE-2014-0627/index.md)
```

## Sources

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

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