{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16188 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16188 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16188 is a high-severity vulnerability in n/a, published on 25 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-16188 and fix it if it is affected.\n\nWhat it is: CVE-2019-16188 is a high-severity vulnerability in n/a, published on 25 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-16188 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-16188/ (Markdown: https://insights.sbomify.com/CVE-2019-16188/index.md)","id":"CVE-2019-16188","markdown":"https://insights.sbomify.com/CVE-2019-16188/index.md","name":"CVE-2019-16188","record":{"aliases":["GHSA-c62w-57vg-xgvp"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"HCL AppScan Source","requires_auth":"none","summary":"An attacker can exfiltrate local files or cause denial of service by tricking a victim into opening a malicious .ozasmt file in HCL AppScan Source.","user_interaction":"required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"appscan_source","vendor":"hcltech"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"HCL AppScan Source before 9.03.13 is susceptible to XML External Entity (XXE) attacks in multiple locations. In particular, an attacker can send a specially crafted .ozasmt file to a targeted victim and ask the victim to open it. When the victim imports the .ozasmt file in AppScan Source, the content of any file in the local file system (to which the victim as read access) can be exfiltrated to a remote listener under the attacker's control. The product does not disable external XML Entity Processing, which can lead to information disclosure and denial of services attacks.","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":"XML external entity in n/a","id":"CVE-2019-16188","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xxe","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2019-16190"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-16187"},"products":["n/a"],"published":"2019-09-25","related":[{"cvss_score":4.8,"headline":"HCL AppScan Source is affected by an expired TLS/SSL certificate","id":"CVE-2024-30149","kev_date_added":null,"published":"2024-10-31"},{"cvss_score":4.8,"headline":"Cross-site scripting in AppScan Source","id":"CVE-2019-4388","kev_date_added":null,"published":"2019-12-18"}],"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-05","vendors":["n/a"]},"summary":"An attacker can exfiltrate local files or cause denial of service by tricking a victim into opening a malicious .ozasmt file in HCL AppScan Source.","url":"https://insights.sbomify.com/CVE-2019-16188/"}