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

> Remote attackers can obtain sensitive information due to misinterpreted SSL compliance settings in IBM Security Access Manager reverse-proxy features.

- **Severity:** Low 3.3 (`AV:A/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:** 21 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w55w-gm2f-2hg5

## What is CVE-2014-3052?

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

### Official description

The reverse-proxy feature in IBM Security Access Manager (ISAM) for Web 8.0 with firmware 8.0.0.2 and 8.0.0.3 interprets the jct-nist-compliance parameter in the opposite of the intended manner, which makes it easier for remote attackers to obtain sensitive information by leveraging weak SSL encryption settings that lack NIST SP 800-131A compliance.

Weakness: CWE-16

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

It affects 2 products.


Products: Ibm Security Access Manager for Web 8.0 Firmware, Ibm Security Access Manager for Web Appliance.

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

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

## Is CVE-2014-3052 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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