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

> Attackers can achieve remote code execution on the web server via a file inclusion vulnerability in Symantec Messaging Gateway.

- **Severity:** Medium 6.6 (`CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5p9r-p6jh-jxvh

## What is CVE-2017-6325?

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.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Symantec Messaging Gateway.

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

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

## Is CVE-2017-6325 being exploited?

There is no known exploitation of CVE-2017-6325 in the wild and no public exploit code.

## Other vulnerabilities in Symantec Corporation Messaging Gateway

- [CVE-2017-6326](https://insights.sbomify.com/CVE-2017-6326/): Code injection in Messaging Gateway (critical 10.0)
- [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)

## Fix prompt for AI coding agents

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

What 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.
Exploitation: There is no known exploitation of CVE-2017-6325 in the wild and no public exploit code.

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

## Sources

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

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