CVE-2016-5310 : Detail

CVE-2016-5310

5.5
/
Medium
Overflow
0.63%V3
Local
2017-04-14
16h00 +00:00
2017-04-14
14h57 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

The RAR file parser component in the AntiVirus Decomposer engine in Symantec Advanced Threat Protection: Network (ATP); Symantec Email Security.Cloud; Symantec Data Center Security: Server; Symantec Endpoint Protection (SEP) for Windows before 12.1.6 MP5; Symantec Endpoint Protection (SEP) for Mac; Symantec Endpoint Protection (SEP) for Linux before 12.1.6 MP6; Symantec Endpoint Protection for Small Business Enterprise (SEP SBE/SEP.Cloud); Symantec Endpoint Protection Cloud (SEPC) for Windows/Mac; Symantec Endpoint Protection Small Business Edition 12.1; CSAPI before 10.0.4 HF02; Symantec Protection Engine (SPE) before 7.0.5 HF02, 7.5.x before 7.5.4 HF02, 7.5.5 before 7.5.5 HF01, and 7.8.x before 7.8.0 HF03; Symantec Mail Security for Domino (SMSDOM) before 8.0.9 HF2.1, 8.1.x before 8.1.2 HF2.3, and 8.1.3 before 8.1.3 HF2.2; Symantec Mail Security for Microsoft Exchange (SMSMSE) before 6.5.8_3968140 HF2.3, 7.x before 7.0_3966002 HF2.1, and 7.5.x before 7.5_3966008 VHF2.2; Symantec Protection for SharePoint Servers (SPSS) before SPSS_6.0.3_To_6.0.5_HF_2.5 update, 6.0.6 before 6.0.6 HF_2.6, and 6.0.7 before 6.0.7_HF_2.7; Symantec Messaging Gateway (SMG) before 10.6.2; Symantec Messaging Gateway for Service Providers (SMG-SP) before 10.5 patch 260 and 10.6 before patch 259; Symantec Web Gateway; and Symantec Web Security.Cloud allows remote attackers to cause a denial of service (memory corruption) via a crafted RAR file that is mishandled during decompression.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-787 Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 5.5 MEDIUM CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

None

There is no loss of confidentiality within the impacted component.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

 [email protected]
V2 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Exploit information

Exploit Database EDB-ID : 40405

Publication date : 2016-09-20 22h00 +00:00
Author : Google Security Research
EDB Verified : Yes

Source: https://bugs.chromium.org/p/project-zero/issues/detail?id=867 In issue 810 we pointed out to Symantec that they hadn't updated their unrar based unpacker for years, and it was vulnerable to dozens of publicly documented flaws. I had expected Symantec to rebase on 5.4.2 (the latest version as of this writing), but they appear to have just backported fixes for the few issues I sent them. Here are two known bugs in unrar that are fixed upstream, but not in Symantec's ancient code. If they continue to refuse to rebase, this might take a few iterations to shake the bugs out. Sigh. As in issue 810, these are remote code execution vulnerabilities at the highest possible privilege level. Proof of Concept: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/40405.zip

Products Mentioned

Configuraton 0

Broadcom>>Symantec_data_center_security_server >> Version -

Symantec>>Advanced_threat_protection >> Version -

    Symantec>>Csapi >> Version To (including) 10.0.4

    Symantec>>Email_security.cloud >> Version -

      Symantec>>Endpoint_protection >> Version To (including) 12.1.4

        Symantec>>Endpoint_protection >> Version To (including) 12.1.6

        Symantec>>Endpoint_protection >> Version To (including) 12.1.6

          Symantec>>Endpoint_protection_cloud >> Version -

            Symantec>>Endpoint_protection_cloud >> Version -

              Symantec>>Endpoint_protection_for_small_business >> Version To (including) 12.1

                Symantec>>Endpoint_protection_for_small_business >> Version -

                  Symantec>>Mail_security_for_domino >> Version To (including) 8.0.9

                  Symantec>>Mail_security_for_domino >> Version 8.1.2

                  Symantec>>Mail_security_for_domino >> Version 8.1.3

                  Symantec>>Mail_security_for_microsoft_exchange >> Version To (including) 6.5.8

                  Symantec>>Mail_security_for_microsoft_exchange >> Version 7.0

                  Symantec>>Mail_security_for_microsoft_exchange >> Version 7.0.1

                  Symantec>>Mail_security_for_microsoft_exchange >> Version 7.0.2

                  Symantec>>Mail_security_for_microsoft_exchange >> Version 7.0.3

                  Symantec>>Mail_security_for_microsoft_exchange >> Version 7.0.4

                  Symantec>>Mail_security_for_microsoft_exchange >> Version 7.5

                  Symantec>>Mail_security_for_microsoft_exchange >> Version 7.5.1

                  Symantec>>Mail_security_for_microsoft_exchange >> Version 7.5.2

                  Symantec>>Mail_security_for_microsoft_exchange >> Version 7.5.3

                  Symantec>>Mail_security_for_microsoft_exchange >> Version 7.5.4

                  Symantec>>Messaging_gateway >> Version To (including) 10.6.1

                  Symantec>>Messaging_gateway_for_service_providers >> Version 10.5

                    Symantec>>Messaging_gateway_for_service_providers >> Version 10.6

                      Symantec>>Protection_engine >> Version To (including) 7.0.5

                      Symantec>>Protection_engine >> Version 7.5.0

                      Symantec>>Protection_engine >> Version 7.5.1

                      Symantec>>Protection_engine >> Version 7.5.2

                      Symantec>>Protection_engine >> Version 7.5.3

                      Symantec>>Protection_engine >> Version 7.5.4

                      Symantec>>Protection_engine >> Version 7.5.5

                      Symantec>>Protection_engine >> Version 7.8.0

                      Symantec>>Protection_for_sharepoint_servers >> Version 6.0.3

                      Symantec>>Protection_for_sharepoint_servers >> Version 6.0.4

                      Symantec>>Protection_for_sharepoint_servers >> Version 6.0.5

                      Symantec>>Protection_for_sharepoint_servers >> Version 6.0.6

                      Symantec>>Protection_for_sharepoint_servers >> Version 6.0.7

                      Symantec>>Web_gateway >> Version -

                        Symantec>>Web_security.cloud >> Version -

                          References

                          http://www.securitytracker.com/id/1036848
                          Tags : vdb-entry, x_refsource_SECTRACK
                          https://www.exploit-db.com/exploits/40405/
                          Tags : exploit, x_refsource_EXPLOIT-DB
                          http://www.securityfocus.com/bid/92866
                          Tags : vdb-entry, x_refsource_BID
                          http://www.securitytracker.com/id/1036849
                          Tags : vdb-entry, x_refsource_SECTRACK
                          http://www.securitytracker.com/id/1036847
                          Tags : vdb-entry, x_refsource_SECTRACK
                          http://www.securitytracker.com/id/1036850
                          Tags : vdb-entry, x_refsource_SECTRACK