# CVE-2017-6326: Code injection in Messaging Gateway

> Attackers can execute arbitrary commands remotely on Symantec Messaging Gateway servers, requiring immediate patching.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5pf7-r489-5rgm

## What is CVE-2017-6326?

CVE-2017-6326 is a critical code injection vulnerability in Symantec Corporation Messaging Gateway, published on 26 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Symantec Messaging Gateway 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.

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

It affects 1 product.


Products: Symantec Messaging Gateway.

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

No fix has been published for CVE-2017-6326 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-6326 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-6326 exists.

Public exploit code:

- Symantec Messaging Gateway Remote Code Execution (metasploit)
- Symantec Messaging Gateway 10.6.2-7 - Remote Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in Symantec Corporation Messaging Gateway

- [CVE-2018-12242](https://insights.sbomify.com/CVE-2018-12242/): Auth bypass in Symantec Messaging Gateway (critical 9.8)
- [CVE-2018-12243](https://insights.sbomify.com/CVE-2018-12243/): XML external entity in Symantec Messaging Gateway (high 8.8)
- [CVE-2016-2204](https://insights.sbomify.com/CVE-2016-2204/): Command injection in n/a (high 8.2)
- [CVE-2012-3579](https://insights.sbomify.com/CVE-2012-3579/): Hardcoded credentials in n/a (high 7.9)
- [CVE-2016-2203](https://insights.sbomify.com/CVE-2016-2203/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6326 is a critical code injection vulnerability in Symantec Corporation Messaging Gateway, published on 26 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-6326 exists.

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-6326/ (Markdown: https://insights.sbomify.com/CVE-2017-6326/index.md)
```

## Sources

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

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