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

> Weak cipher suites in Juniper SSL VPN devices allow remote attackers to sniff network traffic and obtain sensitive information.

- **Severity:** Medium 5.0 (`AV:N/AC:L/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:** No
- **Published:** 13 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j6f4-5ggj-5x99

## What is CVE-2014-3812?

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

### Official description

The Juniper Junos Pulse Secure Access Service (SSL VPN) devices with IVE OS before 7.4r5 and 8.x before 8.0r1 and Junos Pulse Access Control Service (UAC) before 4.4r5 and 5.x before 5.0r1 enable cipher suites with weak encryption algorithms, which make it easier for remote attackers to obtain sensitive information by sniffing the network.

Weakness: CWE-310

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

It affects 18 products.


Products: Juniper Fips Infranet Controller 6500, Juniper Fips Secure Access 4000, Juniper Fips Secure Access 4500, Juniper Fips Secure Access 6000, Juniper Fips Secure Access 6500, Juniper Infranet Controller 4000, Juniper Infranet Controller 4500, Juniper Infranet Controller 6000, Juniper Infranet Controller 6500, Juniper Ive Os, Juniper Mag2600 Gateway, Juniper Mag4610 Gateway, Juniper Mag6610 Gateway, Juniper Mag6611 Gateway, Juniper Secure Access 2500, Juniper Secure Access 4500, Juniper Secure Access 700, Juniper Unified Access Control Software.

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

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

## Is CVE-2014-3812 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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