{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-4650 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4650 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4650 is a medium-severity SQL injection vulnerability in Ibm Maximo Asset Management, published on 26 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-4650 and fix it if it is affected.\n\nWhat it is: CVE-2019-4650 is a medium-severity SQL injection vulnerability in Ibm Maximo Asset Management, published on 26 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-4650 in the wild and no public exploit code.\n\nAffected product: Ibm Maximo Asset Management. 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-4650/ (Markdown: https://insights.sbomify.com/CVE-2019-4650/index.md)","id":"CVE-2019-4650","markdown":"https://insights.sbomify.com/CVE-2019-4650/index.md","name":"CVE-2019-4650","record":{"aliases":["GHSA-3wp3-9r5c-77fc"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Maximo Asset Management","requires_auth":"low_privilege","summary":"Remote attackers can execute SQL injection to view, add, modify, or delete database information in IBM Maximo Asset Management.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"maximo_asset_management","vendor":"ibm"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/A:L/AV:N/AC:L/I:L/UI:N/S:U/C:L/PR:L/RL:O/RC:C/E:U","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"IBM Maximo Asset Management 7.6.1.1 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 170961.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-09-26","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-09-26T11:03:25Z","kind":"github_poc","ref":"https://github.com/aneeshanilkumar89/Maximo_Sql_Injection-CVE-2019-4650","stars":0,"title":"MAximo SQL Injection Time Based - Oracle DB"}],"tier":"poc_unverified"},"has_fix":null,"headline":"SQL injection in Maximo Asset Management","id":"CVE-2019-4650","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:maximo_asset_management","products":["ibm:maximo_asset_management"],"type":"sql_injection","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in Jazz Reporting Service (JRS)","id":"CVE-2019-4651"},"packages":[],"prev":{"headline":"Cross-site scripting in Cognos Analytics","id":"CVE-2019-4645"},"products":["Maximo Asset Management"],"published":"2020-06-26","related":[{"cvss_score":9.8,"headline":"Auth bypass in Maximo Asset Management","id":"CVE-2020-4493","kev_date_added":null,"published":"2020-10-05"},{"cvss_score":9.8,"headline":"SQL injection in Maximo Asset Management","id":"CVE-2017-1175","kev_date_added":null,"published":"2017-07-05"},{"cvss_score":8.8,"headline":"Deserialization in Maximo Asset Management","id":"CVE-2020-4521","kev_date_added":null,"published":"2020-09-15"},{"cvss_score":8.8,"headline":"Hardcoded credentials in Maximo Asset Management","id":"CVE-2018-1524","kev_date_added":null,"published":"2018-08-03"},{"cvss_score":8.8,"headline":"SQL injection in Maximo Asset Management","id":"CVE-2018-1414","kev_date_added":null,"published":"2018-02-22"},{"cvss_score":8.8,"headline":"File upload in Maximo Asset Management","id":"CVE-2017-1499","kev_date_added":null,"published":"2018-02-14"},{"cvss_score":8.8,"headline":"Command injection in Maximo Asset Management","id":"CVE-2016-9984","kev_date_added":null,"published":"2017-06-13"}],"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["IBM"]},"summary":"Remote attackers can execute SQL injection to view, add, modify, or delete database information in IBM Maximo Asset Management.","url":"https://insights.sbomify.com/CVE-2019-4650/"}