{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-3735 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-3735 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-3735 is a high-severity vulnerability in Piwigo Piwigo, published on 28 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-3735 and fix it if it is affected.\n\nWhat it is: CVE-2016-3735 is a high-severity vulnerability in Piwigo Piwigo, published on 28 Jan 2022. 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-2016-3735 in the wild and no public exploit code.\n\nAffected product: Piwigo Piwigo. 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-2016-3735/ (Markdown: https://insights.sbomify.com/CVE-2016-3735/index.md)","id":"CVE-2016-3735","markdown":"https://insights.sbomify.com/CVE-2016-3735/index.md","name":"CVE-2016-3735","record":{"aliases":["GHSA-82rp-xg3c-hxpx"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Piwigo image gallery","requires_auth":"none","summary":"An attacker can predict password reset tokens due to weak random number generation, allowing account takeover if an admin email is known.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"piwigo","vendor":"piwigo"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-335","name":"Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)"}],"description":"Piwigo is image gallery software written in PHP. When a criteria is not met on a host, piwigo defaults to usingmt_rand in order to generate password reset tokens. mt_rand output can be predicted after recovering the seed used to generate it. This low an unauthenticated attacker to take over an account providing they know an administrators email address in order to be able to request password reset.","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":"Weak cryptography in Piwigo","id":"CVE-2016-3735","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"piwigo:piwigo","products":["piwigo:piwigo"],"type":"weak_cryptography","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2016-3736"},"packages":[],"prev":{"headline":"Moodle Cross-site request forgery (CSRF) vulnerability","id":"CVE-2016-3734"},"products":["Piwigo"],"published":"2022-01-28","related":[{"cvss_score":10,"headline":"Unspecified vulnerability in Piwigo before 2.6.3 has unknown impact and attack vectors, related to a \"security failure.\"","id":"CVE-2014-4648","kev_date_added":null,"published":"2014-06-28"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-33361","kev_date_added":null,"published":"2023-05-23"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-33362","kev_date_added":null,"published":"2023-05-23"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-19213","kev_date_added":null,"published":"2022-05-06"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2021-32615","kev_date_added":null,"published":"2021-05-13"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2017-10682","kev_date_added":null,"published":"2017-06-29"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2016-10105","kev_date_added":null,"published":"2017-01-03"}],"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-08-06","vendors":["n/a"]},"summary":"An attacker can predict password reset tokens due to weak random number generation, allowing account takeover if an admin email is known.","url":"https://insights.sbomify.com/CVE-2016-3735/"}