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

> Attackers can sniff network traffic to steal credentials when imapsync falls back to cleartext login after TLS certificate verification fails.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/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:** Yes
- **Published:** 18 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-66m3-3h5c-j36m, MGASA-2014-0106

## What is CVE-2014-2014?

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

### Official description

imapsync before 1.584, when running with the --tls option, attempts a cleartext login when a certificate verification failure occurs, which allows remote attackers to obtain credentials by sniffing the network.

Weakness: CWE-255

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

It affects 1 product.


Products: Imapsync Project Imapsync.

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

Upgrade to a fixed version.

## Is CVE-2014-2014 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-34204](https://insights.sbomify.com/CVE-2023-34204/): Path traversal in n/a (medium 6.5)
- [CVE-2013-4279](https://insights.sbomify.com/CVE-2013-4279/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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