CVE-2013-4102 Weak cryptography in n/a
Critical 9.1
Published
Updated
Check this codebase for CVE-2013-4102 and fix it if it is affected.
What it is: CVE-2013-4102 is a critical vulnerability in n/a, published on 4 Nov 2019. 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-2013-4102 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-2013-4102/ (Markdown: https://insights.sbomify.com/CVE-2013-4102/index.md)
Cryptocat uses a weak random number generator, potentially allowing attackers to predict keys and bypass encryption security.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2013-4102?
CVE-2013-4102 is a critical vulnerability in n/a, published on 4 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Cryptocat before 2.0.22 strophe.js Math.random() Random Number Generator Weakness
Weakness: CWE-330
Which versions are affected by CVE-2013-4102?
It affects 1 product.
Products include Cryptocat Project Cryptocat.
How do I fix CVE-2013-4102?
No fix has been published for CVE-2013-4102 yet. Limit exposure of the affected software until one is available.
Is CVE-2013-4102 being exploited?
There is no known exploitation of CVE-2013-4102 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2013-4108 Multiple unspecified vulnerabilities in Cryptocat Project Cryptocat 2.0.18 have unknown impact and attack vectors.
- CVE-2013-2259 Code injection in Cryptocat
- CVE-2013-2260 Weak cryptography in Cryptocat
- CVE-2013-4103 Cross-site scripting in n/a
- CVE-2013-2257 Weak cryptography in Cryptocat
Sources
Also known as GHSA-jvj5-m3q2-46qm.