{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-52290 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-52290 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-52290 is a high-severity SQL injection vulnerability in Apache StreamPark (incubating), published on 16 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-52290 and fix it if it is affected.\n\nWhat it is: CVE-2023-52290 is a high-severity SQL injection vulnerability in Apache StreamPark (incubating), published on 16 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-52290 in the wild and no public exploit code.\n\nAffected product: Apache StreamPark (incubating). 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-2023-52290/ (Markdown: https://insights.sbomify.com/CVE-2023-52290/index.md)","id":"CVE-2023-52290","markdown":"https://insights.sbomify.com/CVE-2023-52290/index.md","name":"CVE-2023-52290","record":{"aliases":["GHSA-jx5v-m5q5-f9w9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache StreamPark","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit unvalidated sort fields in Apache StreamPark to perform SQL injection and leak data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"streampark","vendor":"apache"}],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"In streampark-console the list pages(e.g: application pages), users can sort page by field. This sort field is sent from the front-end to the back-end, and the SQL query is generated using this field. However, because this sort field isn't validated, there is a risk of SQL injection vulnerability. The attacker must successfully log into the system to launch an attack, which may cause data leakage. Since no data will be written, so this is a low-impact vulnerability.\n\nMitigation:\n\nall users should upgrade to 2.1.4,  Such parameters will be blocked.","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":"Apache StreamPark (incubating): Unchecked SQL query fields trigger SQL injection vulnerability","id":"CVE-2023-52290","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Apache StreamPark (incubating): Unchecked maven build params could trigger remote command execution","id":"CVE-2023-52291"},"packages":[],"prev":{"headline":"Path traversal in flaskcode","id":"CVE-2023-52289"},"products":["Apache StreamPark (incubating)"],"published":"2024-07-16","related":[{"cvss_score":9.8,"headline":"Apache StreamPark (incubating): Upload any file to any directory","id":"CVE-2022-45802","kev_date_added":null,"published":"2023-05-01"},{"cvss_score":9.1,"headline":"Apache StreamPark: session not invalidated after logout","id":"CVE-2024-29070","kev_date_added":null,"published":"2024-07-23"},{"cvss_score":9.1,"headline":"Apache StreamPark (incubating): Logic error causing any account reset","id":"CVE-2022-46365","kev_date_added":null,"published":"2023-05-01"},{"cvss_score":8.8,"headline":"Apache StreamPark: FreeMarker SSTI RCE Vulnerability","id":"CVE-2024-29178","kev_date_added":null,"published":"2024-07-18"},{"cvss_score":8.8,"headline":"Apache StreamPark (incubating): Unchecked maven build params could trigger remote command execution","id":"CVE-2023-52291","kev_date_added":null,"published":"2024-07-17"},{"cvss_score":8.8,"headline":"Apache StreamPark (incubating): maven build params could trigger remote command execution","id":"CVE-2024-29737","kev_date_added":null,"published":"2024-07-17"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-13","vendors":["Apache Software Foundation"]},"summary":"Authenticated attackers can exploit unvalidated sort fields in Apache StreamPark to perform SQL injection and leak data.","url":"https://insights.sbomify.com/CVE-2023-52290/"}