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

> Weak DES password hashing allows attackers to brute-force credentials and gain privileged access to EMC Cloud Tiering and File Management Appliances.

- **Severity:** Medium 4.7 (`AV:L/AC:M/Au:N/C:C/I:N/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:** 17 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r3q4-vf4g-f73m

## What is CVE-2014-0645?

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

### Official description

EMC Cloud Tiering Appliance (CTA) 9.x through 10 SP1 and File Management Appliance (FMA) 7.x store DES password hashes for the root, super, and admin accounts, which makes it easier for context-dependent attackers to obtain sensitive information via a brute-force attack.

Weakness: CWE-255

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

It affects 4 products.


Products: Emc Cloud Tiering Appliance, Emc Cloud Tiering Appliance Software, Emc File Management Appliance, Emc File Management Appliance Software.

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

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

## Is CVE-2014-0645 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-0644](https://insights.sbomify.com/CVE-2014-0644/): XML external entity in n/a (high 7.8)
- [CVE-2012-2285](https://insights.sbomify.com/CVE-2012-2285/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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