{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-6325 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-6325 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-6325 is a medium-severity code injection vulnerability in Symantec Corporation Messaging Gateway, published on 26 Jun 2017. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-6325 and fix it if it is affected.\n\nWhat it is: CVE-2017-6325 is a medium-severity code injection vulnerability in Symantec Corporation Messaging Gateway, published on 26 Jun 2017. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-6325 in the wild and no public exploit code.\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-6325/ (Markdown: https://insights.sbomify.com/CVE-2017-6325/index.md)","id":"CVE-2017-6325","markdown":"https://insights.sbomify.com/CVE-2017-6325/index.md","name":"CVE-2017-6325","record":{"aliases":["GHSA-5p9r-p6jh-jxvh"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Symantec Messaging Gateway","requires_auth":"high_privilege","summary":"Attackers can achieve remote code execution on the web server via a file inclusion vulnerability in Symantec Messaging Gateway.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"symantec","cpe":[{"product":"messaging_gateway","vendor":"symantec"}],"cvss":{"score":6.6,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The Symantec Messaging Gateway can encounter a file inclusion vulnerability, which is a type of vulnerability that is most commonly found to affect web applications that rely on a scripting run time. This issue is caused when an application builds a path to executable code using an attacker-controlled variable in a way that allows the attacker to control which file is executed at run time. This file inclusion vulnerability subverts how an application loads code for execution. Successful exploitation of a file inclusion vulnerability will result in remote code execution on the web server that runs the affected web application.","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":"Code injection in Messaging Gateway","id":"CVE-2017-6325","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in Messaging Gateway","id":"CVE-2017-6326"},"packages":[],"prev":{"headline":"Security feature bypass in Messaging Gateway","id":"CVE-2017-6324"},"products":["Messaging Gateway"],"published":"2017-06-26","related":[{"cvss_score":10,"headline":"Code injection in Messaging Gateway","id":"CVE-2017-6326","kev_date_added":null,"published":"2017-06-26"},{"cvss_score":9.8,"headline":"Auth bypass in Symantec Messaging Gateway","id":"CVE-2018-12242","kev_date_added":null,"published":"2018-09-19"},{"cvss_score":8.8,"headline":"XML external entity in Symantec Messaging Gateway","id":"CVE-2018-12243","kev_date_added":null,"published":"2018-09-19"},{"cvss_score":8.2,"headline":"Command injection in n/a","id":"CVE-2016-2204","kev_date_added":null,"published":"2016-04-22"},{"cvss_score":7.9,"headline":"Hardcoded credentials in n/a","id":"CVE-2012-3579","kev_date_added":null,"published":"2012-08-29"},{"cvss_score":7.8,"headline":"Information disclosure in n/a","id":"CVE-2016-2203","kev_date_added":null,"published":"2016-04-22"},{"cvss_score":7.7,"headline":"Missing authorization in n/a","id":"CVE-2012-3580","kev_date_added":null,"published":"2012-08-29"}],"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":["Symantec Corporation"]},"summary":"Attackers can achieve remote code execution on the web server via a file inclusion vulnerability in Symantec Messaging Gateway.","url":"https://insights.sbomify.com/CVE-2017-6325/"}