{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16962 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16962 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16962 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-16962 and fix it if it is affected.\n\nWhat it is: CVE-2017-16962 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-16962 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-2017-16962/ (Markdown: https://insights.sbomify.com/CVE-2017-16962/index.md)","id":"CVE-2017-16962","markdown":"https://insights.sbomify.com/CVE-2017-16962/index.md","name":"CVE-2017-16962","record":{"aliases":["GHSA-3cqh-3p38-9v4j"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"CommuniGate Pro WebMail","requires_auth":"none","summary":"Stored XSS in CommuniGate Pro WebMail allows attackers to execute scripts via crafted calendar invites or emails, potentially leading to account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"communigate_pro","vendor":"communigate"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The WebMail components (Crystal, pronto, and pronto4) in CommuniGate Pro before 6.2.1 have stored XSS vulnerabilities via (1) the location or details field of a Google Calendar invitation, (2) a crafted Outlook.com calendar (aka Hotmail Calendar) invitation, (3) e-mail granting access to a directory that has JavaScript in its name, (4) JavaScript in a note name, (5) JavaScript in a task name, or (6) HTML e-mail that is mishandled in the Inbox component.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2017-11-15","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-11-15","kind":"exploitdb","ref":"43177","stars":null,"title":"CommuniGatePro 6.1.16 - Cross-Site Scripting"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2017-16962","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2017-16964"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2017-16961"},"products":["n/a"],"published":"2017-11-27","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-18621","kev_date_added":null,"published":"2018-10-24"}],"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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Stored XSS in CommuniGate Pro WebMail allows attackers to execute scripts via crafted calendar invites or emails, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2017-16962/"}