{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16948 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16948 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16948 is a critical server-side request forgery vulnerability in n/a, published on 13 Nov 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-16948 and fix it if it is affected.\n\nWhat it is: CVE-2019-16948 is a critical server-side request forgery vulnerability in n/a, published on 13 Nov 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-16948 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-16948/ (Markdown: https://insights.sbomify.com/CVE-2019-16948/index.md)","id":"CVE-2019-16948","markdown":"https://insights.sbomify.com/CVE-2019-16948/index.md","name":"CVE-2019-16948","record":{"aliases":["GHSA-v8v6-2chv-gcgp"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Enghouse Web Chat","requires_auth":"none","summary":"Attackers can scan internal network ports via SSRF in Enghouse Web Chat, revealing open ports and internal service visibility.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"web_chat","vendor":"enghouse"}],"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":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"An SSRF issue was discovered in Enghouse Web Chat 6.1.300.31. In any POST request, one can replace the port number at WebServiceLocation=http://localhost:8085/UCWebServices/ with a range of ports to determine what is visible on the internal network (as opposed to what general web traffic would see on the product's host). The response from open ports is different than from closed ports. The product does not allow one to change the protocol: anything except http(s) will throw an error; however, it is the type of error that allows one to determine if a port is open or not.","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":"Server-side request forgery in n/a","id":"CVE-2019-16948","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Business logic in n/a","id":"CVE-2019-16949"},"packages":[],"prev":{"headline":"jackson-databind polymorphic typing issue","id":"CVE-2019-16943"},"products":["n/a"],"published":"2019-11-13","related":[{"cvss_score":6.5,"headline":"Business logic in n/a","id":"CVE-2019-16949","kev_date_added":null,"published":"2019-11-13"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-13972","kev_date_added":null,"published":"2020-09-03"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-16950","kev_date_added":null,"published":"2019-11-13"},{"cvss_score":5.3,"headline":"Server-side request forgery in n/a","id":"CVE-2019-16951","kev_date_added":null,"published":"2019-11-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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can scan internal network ports via SSRF in Enghouse Web Chat, revealing open ports and internal service visibility.","url":"https://insights.sbomify.com/CVE-2019-16948/"}