Menu

Star on GitHub · 3.2k

CVE-2017-6326

10.0 · CRITICAL

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 mac…

Published Jun 26, 2017EPSS 72.76%

Overview

CVE-2017-6326 is a critical-severity vulnerability. It was published on June 26, 2017 and has a CVSS 3.0 base score of 10.0 (CRITICAL).

This vulnerability has a CVSS 3.0 base score of 10.0, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2017-6326?

CVE-2017-6326 is a critical-severity vulnerability. It was published on June 26, 2017 and has a CVSS 3.0 base score of 10.0 (CRITICAL).

How severe is CVE-2017-6326?

This vulnerability has a CVSS 3.0 base score of 10.0, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2017-6326?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-6326?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2017-6326 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2017

View all