{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2018-25107 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"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."},"fix_prompt":"Check this codebase for CVE-2018-25107 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2018-25107 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-25107/ (Markdown: https://insights.sbomify.com/CVE-2018-25107/index.md)","id":"CVE-2018-25107","markdown":"https://insights.sbomify.com/CVE-2018-25107/index.md","name":"CVE-2018-25107","record":{"aliases":["DEBIAN-CVE-2018-25107","GHSA-r3m8-7h2r-2mp6","UBUNTU-CVE-2018-25107"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl random library","requires_auth":"none","summary":"The Perl Crypt::Random::Source library uses insecure random bits, potentially allowing attackers to predict cryptographic values.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Weak cryptography in n/a","id":"CVE-2018-25107","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"WAGO: Denial of service in 750-8xx controller due to uncontrolled resource consumption","id":"CVE-2018-25108"},"packages":[],"prev":{"headline":"webuidesigning NebulaX Theme Legacy.php nebula_send_to_hubspot sql injection","id":"CVE-2018-25106"},"products":["n/a"],"published":"2024-12-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-31","vendors":["n/a"]},"summary":"The Perl Crypt::Random::Source library uses insecure random bits, potentially allowing attackers to predict cryptographic values.","url":"https://insights.sbomify.com/CVE-2018-25107/"}