# CVE-2014-5444: Security feature bypass in n/a

> Geary email client fails to warn users about TLS certificate errors, allowing attackers to perform man-in-the-middle attacks and intercept communications.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-5444, GHSA-j2wr-3798-89rx, MGASA-2014-0500

## What is CVE-2014-5444?

CVE-2014-5444 is a medium-severity vulnerability in n/a, published on 30 Sep 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Geary before 0.6.3 does not present the user with a warning when a TLS certificate error is detected, which makes it easier for remote attackers to conduct man-in-the-middle attacks via a crafted certificate.

Weakness: CWE-310

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

It affects 1 product.


Products: Yorba Geary.

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

Upgrade to a fixed version.

## Is CVE-2014-5444 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-5444 is a medium-severity vulnerability in n/a, published on 30 Sep 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-5444 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-5444/ (Markdown: https://insights.sbomify.com/CVE-2014-5444/index.md)
```

## Sources

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

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