{"answers":{"affected":"4 open source packages ship an affected version, including org.springframework.data:spring-data-jpa. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6652 in the wild and no public exploit code.","fix":"Upgrade org.springframework.data:spring-data-jpa to a fixed version for your release line: 1.9.6 or 1.10.4.","what":"CVE-2016-6652 is a medium-severity SQL injection vulnerability in n/a, published on 5 Oct 2016. 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-6652 and fix it if it is affected.\n\nWhat it is: CVE-2016-6652 is a medium-severity SQL injection vulnerability in n/a, published on 5 Oct 2016. 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-6652 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.data:spring-data-jpa (Maven): affected all versions; fixed in 1.9.6\n- org.springframework.data:spring-data-jpa (Maven): affected all versions; fixed in 1.9.6\n- org.springframework.data:spring-data-jpa (Maven): affected from 1.10.0; fixed in 1.10.4\n- org.springframework.data:spring-data-jpa (Maven): affected from 1.10.0; fixed in 1.10.4\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-6652/ (Markdown: https://insights.sbomify.com/CVE-2016-6652/index.md)","id":"CVE-2016-6652","markdown":"https://insights.sbomify.com/CVE-2016-6652/index.md","name":"CVE-2016-6652","record":{"aliases":["GHSA-xr4v-28rm-pvgw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Java data access library","requires_auth":"none","summary":"Attackers can execute arbitrary JPQL commands via crafted sort parameters in Spring Data JPA repositories using @Query annotations.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"spring_data_jpa","vendor":"pivotal_software"}],"cvss":{"score":5.6,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SQL injection vulnerability in Pivotal Spring Data JPA before 1.9.6 (Gosling SR6) and 1.10.x before 1.10.4 (Hopper SR4), when used with a repository that defines a String query using the @Query annotation, allows attackers to execute arbitrary JPQL commands via a sort instance with a function call.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Neutralization of Special Elements used in an SQL Command Pivotal Spring Data JPA","id":"CVE-2016-6652","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"sql_injection","year":"2016"},"n_packages":4,"n_references":5,"next":{"headline":"Information disclosure in n/a","id":"CVE-2016-6653"},"packages":[{"ecosystem":"Maven","fixed":["1.9.6"],"introduced":["0"],"last_affected":[],"package":"org.springframework.data:spring-data-jpa","purl":null,"source":"GHSA-xr4v-28rm-pvgw"},{"ecosystem":"Maven","fixed":["1.9.6"],"introduced":["0"],"last_affected":[],"package":"org.springframework.data:spring-data-jpa","purl":"pkg:maven/org.springframework.data/spring-data-jpa","source":"GHSA-xr4v-28rm-pvgw"},{"ecosystem":"Maven","fixed":["1.10.4"],"introduced":["1.10.0"],"last_affected":[],"package":"org.springframework.data:spring-data-jpa","purl":null,"source":"GHSA-xr4v-28rm-pvgw"},{"ecosystem":"Maven","fixed":["1.10.4"],"introduced":["1.10.0"],"last_affected":[],"package":"org.springframework.data:spring-data-jpa","purl":"pkg:maven/org.springframework.data/spring-data-jpa","source":"GHSA-xr4v-28rm-pvgw"}],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2016-6651"},"products":["n/a"],"published":"2016-10-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"Attackers can execute arbitrary JPQL commands via crafted sort parameters in Spring Data JPA repositories using @Query annotations.","url":"https://insights.sbomify.com/CVE-2016-6652/"}