{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-15604 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-15604 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15604 is a critical vulnerability in TOKUHIROM Amon2, published on 28 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-15604 and fix it if it is affected.\n\nWhat it is: CVE-2025-15604 is a critical vulnerability in TOKUHIROM Amon2, published on 28 Mar 2026. 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-2025-15604 in the wild and no public exploit code.\n\nAffected product: TOKUHIROM Amon2. 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-15604/ (Markdown: https://insights.sbomify.com/CVE-2025-15604/index.md)","id":"CVE-2025-15604","markdown":"https://insights.sbomify.com/CVE-2025-15604/index.md","name":"CVE-2025-15604","record":{"aliases":["GHSA-7r2j-hgh9-jqqx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl web framework","requires_auth":"none","summary":"Insecure random number generation in Amon2 allows attackers to predict session IDs and CSRF tokens, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"amon2","vendor":"tokuhirom"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-340","name":"Generation of Predictable Numbers or Identifiers"},{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"Amon2 versions before 6.17 for Perl use an insecure random_string implementation for security functions.\n\nIn versions 6.06 through 6.16, the random_string function will attempt to read bytes from the /dev/urandom device, but if that is unavailable then it generates bytes by concatenating a SHA-1 hash seeded with the built-in rand() function, the PID, and the high resolution epoch time.  The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand function is unsuitable for cryptographic usage.\n\nBefore version 6.06, there was no fallback when /dev/urandom was not available.\n\nBefore version 6.04, the random_string function used the built-in rand() function to generate a mixed-case alphanumeric string.\n\nThis function may be used for generating session ids, generating secrets for signing or encrypting cookie session data and generating tokens used for Cross Site Request Forgery (CSRF) protection.","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":"Amon2 versions before 6.17 for Perl use an insecure random_string implementation for security functions","id":"CVE-2025-15604","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Hardcoded Cryptographic Key in Configuration Encryption Mechanism on TP-Link Archer NX200, NX210, NX500 and NX600","id":"CVE-2025-15605"},"packages":[],"prev":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2025-15603"},"products":["Amon2"],"published":"2026-03-28","related":[],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-01","vendors":["TOKUHIROM"]},"summary":"Insecure random number generation in Amon2 allows attackers to predict session IDs and CSRF tokens, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2025-15604/"}