{"answers":{"affected":"6 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-2019-3802 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.11.22 or 2.1.8.","what":"CVE-2019-3802 is a low-severity vulnerability in Spring Data JPA, published on 3 Jun 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-3802 and fix it if it is affected.\n\nWhat it is: CVE-2019-3802 is a low-severity vulnerability in Spring Data JPA, published on 3 Jun 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-3802 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.11.22\n- org.springframework.data:spring-data-jpa (Maven): affected all versions; fixed in 1.11.22\n- org.springframework.data:spring-data-jpa (Maven): affected from 2.0.0; fixed in 2.1.8\n- org.springframework.data:spring-data-jpa (Maven): affected from 2.0.0; fixed in 2.1.8\n- org.springframework.data:spring-data-jpa (Maven): affected from 2.1.0; fixed in 2.1.8\n- org.springframework.data:spring-data-jpa (Maven): affected from 2.1.0; fixed in 2.1.8\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-2019-3802/ (Markdown: https://insights.sbomify.com/CVE-2019-3802/index.md)","id":"CVE-2019-3802","markdown":"https://insights.sbomify.com/CVE-2019-3802/index.md","name":"CVE-2019-3802","record":{"aliases":["GHSA-xggx-fx6w-v7ch"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Spring Data JPA","requires_auth":"low_privilege","summary":"Attackers can retrieve unintended data from Spring Data JPA queries by supplying maliciously crafted example values to specific string matchers.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"spring_data_java_persistance_api","vendor":"pivotal_software"}],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-155","name":"Improper Neutralization of Wildcards or Matching Symbols"}],"description":"This affects Spring Data JPA in versions up to and including 2.1.6, 2.0.14 and 1.11.20. ExampleMatcher using ExampleMatcher.StringMatcher.STARTING, ExampleMatcher.StringMatcher.ENDING or ExampleMatcher.StringMatcher.CONTAINING could return more results than anticipated when a maliciously crafted example value is supplied.","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":"Additional information exposure with Spring Data JPA example matcher","id":"CVE-2019-3802","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":6,"n_references":1,"next":{"headline":"Concourse includes token in CLI authentication callback","id":"CVE-2019-3803"},"packages":[{"ecosystem":"Maven","fixed":["1.11.22"],"introduced":["0"],"last_affected":[],"package":"org.springframework.data:spring-data-jpa","purl":null,"source":"GHSA-xggx-fx6w-v7ch"},{"ecosystem":"Maven","fixed":["1.11.22"],"introduced":["0"],"last_affected":[],"package":"org.springframework.data:spring-data-jpa","purl":"pkg:maven/org.springframework.data/spring-data-jpa","source":"GHSA-xggx-fx6w-v7ch"},{"ecosystem":"Maven","fixed":["2.1.8"],"introduced":["2.0.0"],"last_affected":[],"package":"org.springframework.data:spring-data-jpa","purl":null,"source":"GHSA-xggx-fx6w-v7ch"},{"ecosystem":"Maven","fixed":["2.1.8"],"introduced":["2.0.0"],"last_affected":[],"package":"org.springframework.data:spring-data-jpa","purl":"pkg:maven/org.springframework.data/spring-data-jpa","source":"GHSA-xggx-fx6w-v7ch"},{"ecosystem":"Maven","fixed":["2.1.8"],"introduced":["2.1.0"],"last_affected":[],"package":"org.springframework.data:spring-data-jpa","purl":null,"source":"GHSA-xggx-fx6w-v7ch"},{"ecosystem":"Maven","fixed":["2.1.8"],"introduced":["2.1.0"],"last_affected":[],"package":"org.springframework.data:spring-data-jpa","purl":"pkg:maven/org.springframework.data/spring-data-jpa","source":"GHSA-xggx-fx6w-v7ch"}],"prev":{"headline":"Java Projects using HTTP to fetch dependencies","id":"CVE-2019-3801"},"products":["Spring Data JPA"],"published":"2019-06-03","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-09-17","vendors":["Spring"]},"summary":"Attackers can retrieve unintended data from Spring Data JPA queries by supplying maliciously crafted example values to specific string matchers.","url":"https://insights.sbomify.com/CVE-2019-3802/"}