{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-17822 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-17822 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-17822 is a medium-severity SQL injection vulnerability in Piwigo Piwigo, published on 21 Dec 2017. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-17822 and fix it if it is affected.\n\nWhat it is: CVE-2017-17822 is a medium-severity SQL injection vulnerability in Piwigo Piwigo, published on 21 Dec 2017. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-17822 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-2017-17822/ (Markdown: https://insights.sbomify.com/CVE-2017-17822/index.md)","id":"CVE-2017-17822","markdown":"https://insights.sbomify.com/CVE-2017-17822/index.md","name":"CVE-2017-17822","record":{"aliases":["GHSA-35mg-p597-mvg8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Piwigo photo gallery","requires_auth":"high_privilege","summary":"An attacker can exploit SQL injection in the List Users API to read data from the connected MySQL database.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"piwigo","vendor":"piwigo"}],"cvss":{"score":4.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The List Users API of Piwigo 2.9.2 is vulnerable to SQL Injection via the /admin/user_list_backend.php sSortDir_0 parameter. An attacker can exploit this to gain access to the data in a connected MySQL database.","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":"SQL injection in n/a","id":"CVE-2017-17822","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"piwigo:piwigo","products":["piwigo:piwigo"],"type":"sql_injection","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in n/a","id":"CVE-2017-17823"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-17821"},"products":["n/a"],"published":"2017-12-21","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-05","vendors":["n/a"]},"summary":"An attacker can exploit SQL injection in the List Users API to read data from the connected MySQL database.","url":"https://insights.sbomify.com/CVE-2017-17822/"}