{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-6328 exists.","fix":"No fix has been published for CVE-2017-6328 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-6328 is a high-severity vulnerability in Symantec Corporation Messaging Gateway, published on 11 Aug 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-6328 and fix it if it is affected.\n\nWhat it is: CVE-2017-6328 is a high-severity vulnerability in Symantec Corporation Messaging Gateway, published on 11 Aug 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-6328 exists.\n\nAffected product: Symantec Corporation Messaging Gateway. 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-6328/ (Markdown: https://insights.sbomify.com/CVE-2017-6328/index.md)","id":"CVE-2017-6328","markdown":"https://insights.sbomify.com/CVE-2017-6328/index.md","name":"CVE-2017-6328","record":{"aliases":["GHSA-v26p-6c8q-68r2"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Symantec Messaging Gateway","requires_auth":"none","summary":"Attackers can trick authenticated users into executing unauthorized commands on the Symantec Messaging Gateway web interface.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"symantec","cpe":[{"product":"message_gateway","vendor":"symantec"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Symantec Messaging Gateway before 10.6.3-267 can encounter an issue of cross site request forgery (also known as one-click attack and is abbreviated as CSRF or XSRF), which is a type of malicious exploit of a website where unauthorized commands are transmitted from a user that the web application trusts. A CSRF attack attempts to exploit the trust that a specific website has in a user's browser.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2017-08-09","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-08-09","kind":"exploitdb","ref":"42613","stars":null,"title":"Symantec Messaging Gateway \u003c 10.6.3-267 - Cross-Site Request Forgery"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site request forgery in Messaging Gateway","id":"CVE-2017-6328","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in VIP Access for Desktop","id":"CVE-2017-6329"},"packages":[],"prev":{"headline":"Symantec Messaging Gateway Remote Code Execution","id":"CVE-2017-6327"},"products":["Messaging Gateway"],"published":"2017-08-11","related":[{"cvss_score":8.8,"headline":"Symantec Messaging Gateway Remote Code Execution","id":"CVE-2017-6327","kev_date_added":"2021-11-03","published":"2017-08-11"},{"cvss_score":9.8,"headline":"Privilege escalation in Symantec Messaging Gateway","id":"CVE-2019-12751","kev_date_added":null,"published":"2019-07-11"}],"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-09-16","vendors":["Symantec Corporation"]},"summary":"Attackers can trick authenticated users into executing unauthorized commands on the Symantec Messaging Gateway web interface.","url":"https://insights.sbomify.com/CVE-2017-6328/"}