CVE-2018-25107 Weak cryptography in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2018-25107 and fix it if it is affected.
What it is: CVE-2018-25107 is a high-severity vulnerability in n/a, published on 29 Dec 2024. 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-2018-25107 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-2018-25107/ (Markdown: https://insights.sbomify.com/CVE-2018-25107/index.md)
The Perl Crypt::Random::Source library uses insecure random bits, potentially allowing attackers to predict cryptographic values.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2018-25107?
CVE-2018-25107 is a high-severity vulnerability in n/a, published on 29 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The Crypt::Random::Source package before 0.13 for Perl has a fallback to the built-in rand() function, which is not a secure source of random bits.
Weakness: CWE-338
Which versions are affected by CVE-2018-25107?
How do I fix CVE-2018-25107?
Upgrade to a fixed version.
Is CVE-2018-25107 being exploited?
There is no known exploitation of CVE-2018-25107 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2018-25107, GHSA-r3m8-7h2r-2mp6, UBUNTU-CVE-2018-25107.