# CVE-2015-4953: Weak cryptography in n/a

> Man-in-the-middle attackers can decrypt traffic due to a weakness in the encryption protocol of IBM BigFix Remote Control.

- **Severity:** Medium 4.8 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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:** 29 Mar 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6q4x-jxmf-pjpx

## What is CVE-2015-4953?

CVE-2015-4953 is a medium-severity vulnerability in n/a, published on 29 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM BigFix Remote Control before Interim Fix pack 9.1.2-TIV-IBRC912-IF0001 makes it easier for man-in-the-middle attackers to decrypt traffic by leveraging a weakness in its encryption protocol. IBM X-Force ID: 105197.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2015-4953?

It affects 1 product.


Products: Ibm Bigfix Remote Control.

## How do I fix CVE-2015-4953?

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

## Is CVE-2015-4953 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-2944](https://insights.sbomify.com/CVE-2016-2944/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-2963](https://insights.sbomify.com/CVE-2016-2963/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-2929](https://insights.sbomify.com/CVE-2016-2929/): Weak cryptography in n/a (high 8.1)
- [CVE-2016-2948](https://insights.sbomify.com/CVE-2016-2948/): Hardcoded credentials in n/a (high 7.8)
- [CVE-2016-2930](https://insights.sbomify.com/CVE-2016-2930/): Auth bypass in BigFix Remote Control (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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