{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12374 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12374 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12374 is a high-severity SQL injection vulnerability in n/a, published on 3 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-12374 and fix it if it is affected.\n\nWhat it is: CVE-2019-12374 is a high-severity SQL injection vulnerability in n/a, published on 3 Jun 2019. 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-2019-12374 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2019-12374/ (Markdown: https://insights.sbomify.com/CVE-2019-12374/index.md)","id":"CVE-2019-12374","markdown":"https://insights.sbomify.com/CVE-2019-12374/index.md","name":"CVE-2019-12374","record":{"aliases":["GHSA-fcvv-549h-h48p"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ivanti Endpoint Manager","requires_auth":"none","summary":"SQL injection in Ivanti Endpoint Manager allows attackers to read or modify database contents via unsanitized username input in Basic Authentication.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"landesk_management_suite","vendor":"ivanti"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A SQL Injection vulnerability exists in Ivanti LANDESK Management Suite (LDMS, aka Endpoint Manager) 10.0.1.168 Service Update 5 due to improper username sanitization in the Basic Authentication implementation in core/provisioning.secure/ProvisioningSecure.asmx in Provisioning.Secure.dll.","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 n/a","id":"CVE-2019-12374","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2019-12375"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-12373"},"products":["n/a"],"published":"2019-06-03","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2019-12377","kev_date_added":null,"published":"2019-06-03"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-3147","kev_date_added":null,"published":"2017-01-23"},{"cvss_score":9,"headline":"Information disclosure in n/a","id":"CVE-2019-12373","kev_date_added":null,"published":"2019-06-03"},{"cvss_score":6.3,"headline":"Path traversal in n/a","id":"CVE-2019-12375","kev_date_added":null,"published":"2019-06-03"},{"cvss_score":4.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-12376","kev_date_added":null,"published":"2019-06-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-04","vendors":["n/a"]},"summary":"SQL injection in Ivanti Endpoint Manager allows attackers to read or modify database contents via unsanitized username input in Basic Authentication.","url":"https://insights.sbomify.com/CVE-2019-12374/"}