CVE-2017-6328
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSymantec Messaging Gateway versions prior to 10.6.3-267 contain a Cross-Site Request Forgery (CSRF) vulnerability that allows attackers to execute unauthorized actions by tricking authenticated users into submitting malicious requests, exploiting the application's trust in the user's browser.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 10.6.3-2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the installed version of Symantec Messaging GatewayAccess the SMG admin console by logging into the web interface, then navigate to the Administration or System Settings section to find the version information. Alternatively, access the command line interface on the SMG appliance and run the appropriate command to retrieve the software version (such as 'version' or 'system show version' depending on the available CLI).Affected if Unable to confirm the version is 10.6.3-267 or later through either the web admin interface or CLI.
-
Compare your installed version against the vulnerable rangeNote the exact version number displayed (for example, 10.6.3-2, 10.6.2-456, or similar). Compare this numeric version to the fixed release 10.6.3-267. The product version format typically shows the base release followed by a build number.Affected if The installed version is any build earlier than 10.6.3-267, such as 10.6.3-2 or earlier release branches.
-
Verify the CSRF protection statusSince this is a CSRF vulnerability where the application lacks proper anti-CSRF tokens, inspect whether the SMG admin interface forms include CSRF token parameters in their POST requests. Use browser developer tools to examine form submissions in the admin console.Affected if Admin interface forms submit without any CSRF token or unique request validation parameters.
-
Confirm active user sessions are exposedReview whether authenticated administrators can access the SMG admin panel. The CSRF vulnerability exploits trusted authenticated sessions, so determine if the web admin interface is accessible and actively used.Affected if The SMG admin interface is accessible and users have active authenticated sessions without additional token-based request validation.
You are affected if your installed Symantec Messaging Gateway version is below 10.6.3-267 and the admin web interface is accessible without CSRF token protection in form submissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Symantec Messaging Gateway to version 10.6.3-267 or later to obtain the security patch. Additionally, implement anti-CSRF tokens and validate Origin/Referer headers as defense-in-depth measures.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-6328 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data