# CVE-2017-6327: Symantec Messaging Gateway Remote Code Execution

> Attackers can execute arbitrary commands remotely on Symantec Messaging Gateway, potentially leading to privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-x45p-q5pf-h9jx

## What is CVE-2017-6327?

CVE-2017-6327 is a high-severity command injection vulnerability in Symantec Corporation Messaging Gateway, published on 11 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Symantec Messaging Gateway before 10.6.3-267 can encounter an issue of remote code execution, which describes a situation whereby an individual may obtain the ability to execute commands remotely on a target machine or in a target process. In this type of occurrence, after gaining access to the system, the attacker may attempt to elevate their privileges.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2017-6327?

It affects 1 product.


Products: Symantec Message Gateway.

## How do I fix CVE-2017-6327?

No fix has been published for CVE-2017-6327 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2017-6327 being exploited?

Yes. Attackers have exploited CVE-2017-6327 in the wild since at least 3 Nov 2021.

Public exploit code:

- Symantec Messaging Gateway 10.6.3-2 - Root Remote Command Execution (exploitdb)

## Other vulnerabilities in Symantec Corporation Messaging Gateway

- [CVE-2019-12751](https://insights.sbomify.com/CVE-2019-12751/): Privilege escalation in Symantec Messaging Gateway (critical 9.8)
- [CVE-2017-6328](https://insights.sbomify.com/CVE-2017-6328/): Cross-site request forgery in Messaging Gateway (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6327 and fix it if it is affected.

What it is: CVE-2017-6327 is a high-severity command injection vulnerability in Symantec Corporation Messaging Gateway, published on 11 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-6327 in the wild since at least 3 Nov 2021.

Affected product: Symantec Corporation Messaging Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-6327/ (Markdown: https://insights.sbomify.com/CVE-2017-6327/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6327
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6327
- OSV: https://osv.dev/vulnerability/CVE-2017-6327

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-6327/
Summaries are generated and may contain mistakes; the official description above is the record.
