{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-1828 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-1828 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1828 is a high-severity vulnerability in perl Crypt::Random, published on 10 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-1828 and fix it if it is affected.\n\nWhat it is: CVE-2025-1828 is a high-severity vulnerability in perl Crypt::Random, published on 10 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-1828 in the wild and no public exploit code.\n\nAffected product: perl Crypt::Random. 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-2025-1828/ (Markdown: https://insights.sbomify.com/CVE-2025-1828/index.md)","id":"CVE-2025-1828","markdown":"https://insights.sbomify.com/CVE-2025-1828/index.md","name":"CVE-2025-1828","record":{"aliases":["GHSA-jqxq-7f92-m7ww"],"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":"Perl's Crypt::Random module may use insecure random number generation, weakening cryptographic security, especially on Windows systems.","user_interaction":"required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"crypt\\","vendor":"timlegge"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"},{"id":"CWE-331","name":"Insufficient Entropy"}],"description":"Crypt::Random Perl package 1.05 through 1.55 may use rand() function, which is not cryptographically strong, for cryptographic functions.\n\nIf the Provider is not specified and /dev/urandom or an Entropy Gathering Daemon (egd) service is not available Crypt::Random will default to use the insecure Crypt::Random::rand provider.\n\nIn particular, Windows versions of perl will encounter this issue by default.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Perl's Crypt::Random module after 1.05 and before 1.56 may use rand() function for cryptographic functions","id":"CVE-2025-1828","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"TOTOLINK X18 cstecgi.cgi setMtknatCfg os command injection","id":"CVE-2025-1829"},"packages":[],"prev":{"headline":"IBM Jazz Foundation cross-site scripting","id":"CVE-2025-1826"},"products":["Crypt::Random"],"published":"2025-03-10","related":[{"cvss_score":9.8,"headline":"Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows","id":"CVE-2026-30909","kev_date_added":null,"published":"2026-03-08"},{"cvss_score":9.1,"headline":"Crypt::NaCl::Sodium versions through 2.001 for Perl has an integer overflow flaw on 32-bit systems","id":"CVE-2026-2588","kev_date_added":null,"published":"2026-02-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-09-09","vendors":["perl"]},"summary":"Perl's Crypt::Random module may use insecure random number generation, weakening cryptographic security, especially on Windows systems.","url":"https://insights.sbomify.com/CVE-2025-1828/"}