# CVE-2017-12361: Weak cryptography in Cisco Jabber

> An attacker can decrypt secure communications by exploiting weak random number generation in Cisco Jabber for Windows.

- **Severity:** Medium 4.0 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4998-58vc-p397

## What is CVE-2017-12361?

CVE-2017-12361 is a medium-severity vulnerability in Cisco Jabber, published on 30 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in Cisco Jabber for Windows could allow an unauthenticated, local attacker to access sensitive communications made by the Jabber client. An attacker could exploit this vulnerability to gain information to conduct additional attacks. The vulnerability is due to the way Cisco Jabber for Windows handles random number generation for file folders. An attacker could exploit the vulnerability by fixing the random number data used to establish Secure Sockets Layer (SSL) connections between clients. An exploit could allow the attacker to decrypt secure communications made by the Cisco Jabber for Windows client. Cisco Bug IDs: CSCve44806.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-12361?

It affects 1 product.


Products: Cisco Jabber.

## How do I fix CVE-2017-12361?

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

## Is CVE-2017-12361 being exploited?

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

## Other vulnerabilities in Cisco Jabber

- [CVE-2021-1411](https://insights.sbomify.com/CVE-2021-1411/): Cisco Jabber Desktop and Mobile Client Software Vulnerabilities (critical 9.9)
- [CVE-2021-1417](https://insights.sbomify.com/CVE-2021-1417/): Cisco Jabber Desktop and Mobile Client Software Vulnerabilities (critical 9.9)
- [CVE-2021-1418](https://insights.sbomify.com/CVE-2021-1418/): Cisco Jabber Desktop and Mobile Client Software Vulnerabilities (critical 9.9)
- [CVE-2021-1469](https://insights.sbomify.com/CVE-2021-1469/): Cisco Jabber Desktop and Mobile Client Software Vulnerabilities (critical 9.9)
- [CVE-2021-1471](https://insights.sbomify.com/CVE-2021-1471/): Cisco Jabber Desktop and Mobile Client Software Vulnerabilities (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12361 and fix it if it is affected.

What it is: CVE-2017-12361 is a medium-severity vulnerability in Cisco Jabber, published on 30 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12361 in the wild and no public exploit code.

Affected product: Cisco Jabber. 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-2017-12361/ (Markdown: https://insights.sbomify.com/CVE-2017-12361/index.md)
```

## Sources

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

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