{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16383 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16383 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16383 is a critical SQL injection vulnerability in n/a, published on 24 Sep 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-16383 and fix it if it is affected.\n\nWhat it is: CVE-2019-16383 is a critical SQL injection vulnerability in n/a, published on 24 Sep 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-16383 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-16383/ (Markdown: https://insights.sbomify.com/CVE-2019-16383/index.md)","id":"CVE-2019-16383","markdown":"https://insights.sbomify.com/CVE-2019-16383/index.md","name":"CVE-2019-16383","record":{"aliases":["GHSA-q2wr-68c4-jqq6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Managed File Transfer","requires_auth":"none","summary":"Unauthenticated attackers can exploit SQL injection in the REST API to read or modify database contents in Progress MOVEit Transfer.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"moveit_transfer","vendor":"ipswitch"}],"cvss":{"score":9.4,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"MOVEit.DMZ.WebApi.dll in Progress MOVEit Transfer 2018 SP2 before 10.2.4, 2019 before 11.0.2, and 2019.1 before 11.1.1 allows an unauthenticated attacker to gain unauthorized access to the database. Depending on the database engine being used (MySQL, Microsoft SQL Server, or Azure SQL), an attacker may be able to infer information about the structure and contents of the database, or may be able to alter the database via the REST API, aka SQL Injection.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2020-04-13","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-04-13","kind":"exploitdb","ref":"48316","stars":null,"title":"MOVEit Transfer 11.1.1 - 'token' Unauthenticated SQL Injection"}],"tier":"poc_unverified"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2019-16383","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2019"},"n_packages":0,"n_references":5,"next":{"headline":"Path traversal in n/a","id":"CVE-2019-16384"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-16382"},"products":["n/a"],"published":"2019-09-24","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-18464","kev_date_added":null,"published":"2019-10-31"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2019-18465","kev_date_added":null,"published":"2019-10-31"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Unauthenticated attackers can exploit SQL injection in the REST API to read or modify database contents in Progress MOVEit Transfer.","url":"https://insights.sbomify.com/CVE-2019-16383/"}