{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-48597 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-48597 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-48597 is a high-severity SQL injection vulnerability in ScienceLogic SL 1, published on 9 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-48597 and fix it if it is affected.\n\nWhat it is: CVE-2022-48597 is a high-severity SQL injection vulnerability in ScienceLogic SL 1, published on 9 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-48597 in the wild and no public exploit code.\n\nAffected product: ScienceLogic SL 1. 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-2022-48597/ (Markdown: https://insights.sbomify.com/CVE-2022-48597/index.md)","id":"CVE-2022-48597","markdown":"https://insights.sbomify.com/CVE-2022-48597/index.md","name":"CVE-2022-48597","record":{"aliases":["GHSA-ww99-c4f4-9w6h"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SL1 monitoring platform","requires_auth":"low_privilege","summary":"Attackers can inject arbitrary SQL via the ticket event report feature to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Securifera","cpe":[{"product":"sl1","vendor":"sciencelogic"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"},{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"A SQL injection vulnerability exists in the “ticket event report” feature of the ScienceLogic SL1 that takes unsanitized user‐controlled input and passes it directly to a SQL query. This allows for the injection of arbitrary SQL before being executed against the 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":null,"headline":"SQL injection in SL 1","id":"CVE-2022-48597","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in SL 1","id":"CVE-2022-48598"},"packages":[],"prev":{"headline":"SQL injection in SL 1","id":"CVE-2022-48596"},"products":["SL 1"],"published":"2023-08-09","related":[{"cvss_score":9.3,"headline":"ScienceLogic SL1 Unspecified","id":"CVE-2024-9537","kev_date_added":"2024-10-21","published":"2024-10-18"},{"cvss_score":8.8,"headline":"Command injection in SL 1","id":"CVE-2022-48580","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":8.8,"headline":"Command injection in SL 1","id":"CVE-2022-48581","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":8.8,"headline":"Command injection in SL 1","id":"CVE-2022-48582","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":8.8,"headline":"Command injection in SL 1","id":"CVE-2022-48583","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":8.8,"headline":"Command injection in SL 1","id":"CVE-2022-48584","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":8.8,"headline":"SQL injection in SL 1","id":"CVE-2022-48585","kev_date_added":null,"published":"2023-08-09"}],"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-10-10","vendors":["ScienceLogic"]},"summary":"Attackers can inject arbitrary SQL via the ticket event report feature to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2022-48597/"}