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

> Remote attackers can downgrade TLS signature algorithm negotiations in PolarSSL, weakening connection 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:** Yes
- **Published:** 24 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9jjq-g2xm-68mw

## What is CVE-2014-8627?

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

### Official description

PolarSSL 1.3.8 does not properly negotiate the signature algorithm to use, which allows remote attackers to conduct downgrade attacks via unspecified vectors.

Weakness: CWE-310

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

It affects 1 product.


Products: Polarssl Polarssl.

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

Upgrade to a fixed version.

## Is CVE-2014-8627 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-4574](https://insights.sbomify.com/CVE-2011-4574/): Weak cryptography in PolarSSL (critical 9.8)
- [CVE-2014-8628](https://insights.sbomify.com/CVE-2014-8628/): Denial of service in n/a (high 7.8)
- [CVE-2013-5914](https://insights.sbomify.com/CVE-2013-5914/): Buffer overflow in the ssl_read_record function in ssl_tls.c in PolarSSL before 1.1.8, when using TLS 1.1, might allow remote attackers to e (medium 6.8)
- [CVE-2013-5915](https://insights.sbomify.com/CVE-2013-5915/): Information disclosure in n/a (medium 4.3)
- [CVE-2013-4623](https://insights.sbomify.com/CVE-2013-4623/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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