{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2013-7372 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-7372 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-7372 is a medium-severity vulnerability in Google Android, published on 29 Apr 2014. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-7372 and fix it if it is affected.\n\nWhat it is: CVE-2013-7372 is a medium-severity vulnerability in Google Android, published on 29 Apr 2014. 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-2013-7372 in the wild and no public exploit code.\n\nAffected product: Google Android. 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-2013-7372/ (Markdown: https://insights.sbomify.com/CVE-2013-7372/index.md)","id":"CVE-2013-7372","markdown":"https://insights.sbomify.com/CVE-2013-7372/index.md","name":"CVE-2013-7372","record":{"aliases":["GHSA-fgwm-j3p8-w23c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Java security library","requires_auth":"none","summary":"Attackers can predict random numbers due to a flawed PRNG implementation, compromising cryptographic security in applications like Bitcoin wallets.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"harmony","vendor":"apache"},{"product":"android","vendor":"google"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"The engineNextBytes function in classlib/modules/security/src/main/java/common/org/apache/harmony/security/provider/crypto/SHA1PRNG_SecureRandomImpl.java in the SecureRandom implementation in Apache Harmony through 6.0M3, as used in the Java Cryptography Architecture (JCA) in Android before 4.4 and other products, when no seed is provided by the user, uses an incorrect offset value, which makes it easier for attackers to defeat cryptographic protection mechanisms by leveraging the resulting PRNG predictability, as exploited in the wild against Bitcoin wallet applications in August 2013.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2013-7372","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:android","products":["google:android"],"type":"weak_cryptography","year":"2013"},"n_packages":0,"n_references":4,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2013-7373"},"packages":[],"prev":{"headline":"Node Connect Reflected Cross-Site Scripting in Sencha Labs Connect middleware","id":"CVE-2013-7371"},"products":["n/a"],"published":"2014-04-29","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Attackers can predict random numbers due to a flawed PRNG implementation, compromising cryptographic security in applications like Bitcoin wallets.","url":"https://insights.sbomify.com/CVE-2013-7372/"}