{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-4669 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-4669 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-4669 is a medium-severity SQL injection vulnerability in Ibm Business Automation Workflow, published on 27 Feb 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-4669 and fix it if it is affected.\n\nWhat it is: CVE-2019-4669 is a medium-severity SQL injection vulnerability in Ibm Business Automation Workflow, published on 27 Feb 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-4669 in the wild and no public exploit code.\n\nAffected product: Ibm Business Automation Workflow. 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-4669/ (Markdown: https://insights.sbomify.com/CVE-2019-4669/index.md)","id":"CVE-2019-4669","markdown":"https://insights.sbomify.com/CVE-2019-4669/index.md","name":"CVE-2019-4669","record":{"aliases":["GHSA-r67h-45wp-63r3"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Business Process Manager","requires_auth":"low_privilege","summary":"Remote attackers can inject SQL to view, add, modify, or delete database information in IBM Business Process Manager and Automation Workflow.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"business_automation_workflow","vendor":"ibm"},{"product":"business_process_manager","vendor":"ibm"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/I:L/A:L/AC:L/UI:N/AV:N/PR:L/C:L/S:U/RL:O/E:U/RC:C","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"IBM Business Process Manager 8.5.7.0 through 8.5.7.0 2017.06, 8.6.0.0 through 8.6.0.0 CF2018.03, and IBM Business Automation Workflow 18.0.0.1 through 19.0.0.3 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: 171254.","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 Business Automation Workflow","id":"CVE-2019-4669","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:business_automation_workflow","products":["ibm:business_automation_workflow","ibm:business_process_manager"],"type":"sql_injection","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in WebSphere Application Server","id":"CVE-2019-4670"},"packages":[],"prev":{"headline":"Hardcoded credentials in UrbanCode Deploy","id":"CVE-2019-4668"},"products":["Business Automation Workflow","Business Process Manager"],"published":"2020-02-27","related":[{"cvss_score":7.5,"headline":"IBM Business Automation Workflow information disclosure","id":"CVE-2022-43864","kev_date_added":null,"published":"2023-01-25"},{"cvss_score":7.1,"headline":"XML eXternal Entity injection (XXE) vulnerability affect IBM Business Automation Workflow -","id":"CVE-2025-13096","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":7.1,"headline":"XML external entity in Business Automation Workflow","id":"CVE-2019-4424","kev_date_added":null,"published":"2019-08-20"},{"cvss_score":6.4,"headline":"Cross-site scripting in Business Process Manager Standard","id":"CVE-2021-38893","kev_date_added":null,"published":"2021-12-21"},{"cvss_score":6.4,"headline":"Cross-site scripting in Business Automation Workflow","id":"CVE-2021-29834","kev_date_added":null,"published":"2021-09-29"},{"cvss_score":6.4,"headline":"Cross-site scripting in Business Automation Workflow","id":"CVE-2021-29775","kev_date_added":null,"published":"2021-06-28"},{"cvss_score":6.4,"headline":"Cross-site scripting in Business Automation Workflow","id":"CVE-2020-4698","kev_date_added":null,"published":"2020-09-08"}],"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-09-17","vendors":["IBM"]},"summary":"Remote attackers can inject SQL to view, add, modify, or delete database information in IBM Business Process Manager and Automation Workflow.","url":"https://insights.sbomify.com/CVE-2019-4669/"}