{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16382 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16382 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16382 is a critical command injection vulnerability in n/a, published on 19 Mar 2020. 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-16382 and fix it if it is affected.\n\nWhat it is: CVE-2019-16382 is a critical command injection vulnerability in n/a, published on 19 Mar 2020. 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-16382 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-16382/ (Markdown: https://insights.sbomify.com/CVE-2019-16382/index.md)","id":"CVE-2019-16382","markdown":"https://insights.sbomify.com/CVE-2019-16382/index.md","name":"CVE-2019-16382","record":{"aliases":["GHSA-6774-xm68-55p3"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Ivanti Workspace Control","requires_auth":"none","summary":"Attackers can bypass folder protection to inject malicious XML, leading to arbitrary command execution via PowerGrid.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"workspace_control","vendor":"ivanti"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in Ivanti Workspace Control 10.3.110.0. One is able to bypass Ivanti's FileGuard folder protection by renaming the WMTemp work folder used by PowerGrid. A malicious PowerGrid XML file can then be created, after which the folder is renamed back to its original value. Also, CVE-2018-15591 exploitation can consequently be achieved by using PowerGrid with the /SEE parameter to execute the arbitrary command specified in the XML file.","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":"Command injection in n/a","id":"CVE-2019-16382","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2019-16383"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2019-16378"},"products":["n/a"],"published":"2020-03-19","related":[{"cvss_score":8.8,"headline":"Hardcoded credentials in Workspace Control","id":"CVE-2025-22455","kev_date_added":null,"published":"2025-06-10"},{"cvss_score":8.8,"headline":"Hardcoded credentials in Workspace Control","id":"CVE-2025-5353","kev_date_added":null,"published":"2025-06-10"},{"cvss_score":8.8,"headline":"Privilege escalation in Workspace Control","id":"CVE-2024-44103","kev_date_added":null,"published":"2024-09-10"},{"cvss_score":8.8,"headline":"Auth bypass in Workspace Control","id":"CVE-2024-44104","kev_date_added":null,"published":"2024-09-10"},{"cvss_score":8.8,"headline":"Privilege escalation in Workspace Control","id":"CVE-2024-44106","kev_date_added":null,"published":"2024-09-10"},{"cvss_score":8.8,"headline":"Privilege escalation in Workspace Control","id":"CVE-2024-44107","kev_date_added":null,"published":"2024-09-10"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass folder protection to inject malicious XML, leading to arbitrary command execution via PowerGrid.","url":"https://insights.sbomify.com/CVE-2019-16382/"}