# CVE-2017-6328: Cross-site request forgery in Messaging Gateway

> Attackers can trick authenticated users into executing unauthorized commands on the Symantec Messaging Gateway web interface.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v26p-6c8q-68r2

## What is CVE-2017-6328?

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.

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

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Symantec Message Gateway.

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

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

## Is CVE-2017-6328 being exploited?

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

Public exploit code:

- Symantec Messaging Gateway < 10.6.3-267 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in Symantec Corporation Messaging Gateway

- [CVE-2017-6327](https://insights.sbomify.com/CVE-2017-6327/): Symantec Messaging Gateway Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2019-12751](https://insights.sbomify.com/CVE-2019-12751/): Privilege escalation in Symantec Messaging Gateway (critical 9.8)

## Fix prompt for AI coding agents

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

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-6328 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-6328/ (Markdown: https://insights.sbomify.com/CVE-2017-6328/index.md)
```

## Sources

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

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