English
Français
Light
Dark
System

CVEFind - Alertes CVE

Restez informé en continue
Créer un compte Ouvrez un compte Simple et Gratuit Se connecter Gérez vos alertes

CVE-2016-2209 : Détail

CVE-2016-2209

7.3
/
HIGH
Overflow
3.39%V3
Local
2016-06-30 21:00 +00:00
2017-09-02 07:57 +00:00
CVE.org
NVD

Alerte pour un CVE

Restez informé de toutes modifications pour un CVE spécifique.
Gestion des alertes

Descriptions

Buffer overflow in Dec2SS.dll in the AntiVirus Decomposer engine in Symantec Advanced Threat Protection (ATP); Symantec Data Center Security:Server (SDCS:S) 6.x through 6.6 MP1; Symantec Web Gateway; Symantec Endpoint Protection (SEP) before 12.1 RU6 MP5; Symantec Endpoint Protection (SEP) for Mac; Symantec Endpoint Protection (SEP) for Linux before 12.1 RU6 MP5; Symantec Protection Engine (SPE) before 7.0.5 HF01, 7.5.x before 7.5.3 HF03, 7.5.4 before HF01, and 7.8.0 before HF01; Symantec Protection for SharePoint Servers (SPSS) 6.0.3 through 6.0.5 before 6.0.5 HF 1.5 and 6.0.6 before HF 1.6; Symantec Mail Security for Microsoft Exchange (SMSMSE) before 7.0_3966002 HF1.1 and 7.5.x before 7.5_3966008 VHF1.2; Symantec Mail Security for Domino (SMSDOM) before 8.0.9 HF1.1 and 8.1.x before 8.1.3 HF1.2; CSAPI before 10.0.4 HF01; Symantec Message Gateway (SMG) before 10.6.1-4; Symantec Message Gateway for Service Providers (SMG-SP) 10.5 before patch 254 and 10.6 before patch 253; Norton AntiVirus, Norton Security, Norton Internet Security, and Norton 360 before NGC 22.7; Norton Security for Mac before 13.0.2; Norton Power Eraser (NPE) before 5.1; and Norton Bootable Removal Tool (NBRT) before 2016.1 allows remote attackers to execute arbitrary code via a crafted file.

Informations

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.

Metrics

Metric Score Sévérité CVSS Vecteur Source
V3.0 7.3 HIGH CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/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

A vulnerability exploitable with Local access means that the vulnerable component is not bound to the network stack, and the attacker's path is via read/write/execute capabilities. In some cases, the attacker may be logged in locally in order to exploit the vulnerability, otherwise, she may rely on User Interaction to execute a malicious file.

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 against 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 to carry out an attack.

User Interaction

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

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

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

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

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.

Low

There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is constrained. The information disclosure does not cause a direct, serious loss to 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.

Low

Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is constrained. The data modification does not have a direct, serious impact on 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 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 that one has in the description of a vulnerability.

Environmental Metrics

 [email protected]
V2 9 AV:N/AC:L/Au:N/C:P/I:P/A:C [email protected]

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

EPSS Score

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

EPSS Percentile

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
EPSS First.org

Informations sur l'Exploit

Exploit Database EDB-ID : 40037

Date de publication : 2016-06-28 22:00 +00:00
Auteur : Google Security Research
EDB Vérifié : Yes

Source: https://bugs.chromium.org/p/project-zero/issues/detail?id=823 A PowerPoint PPT file is a complicated OLE compound document comprising of a series of streams. The format is described by Microsoft in [MS-PPT]. https://msdn.microsoft.com/en-us/library/office/cc313106(v=office.12).aspx Symantec have implemented an I/O abstraction layer for seeking within the streams of a compound document, which they use to extract embedded objects like VBA macros and so on. Unfortunately, a bug in this I/O abstraction results in a critical security vulnerability. The bug occurs when a read request can be satisfied from the cache, but from a non-zero start offset. In this case, the request size is always rounded to (CACHE_SIZE - Offset), which may not be correct. For example, a read request that can be satisfied from the stream cache in these ways: +-------------------------+ | CACHE | +-------------------------+ 1. <---------> Non-zero offset, but entire cache needed. 2. <------> Zero offset, but not the entire cache. 3. <----------------------> Entire cache. 4. <----> Non-zero offset and not entire cache. All of these cases work fine except 4, where a buffer overflow occurs, because the request is rounded up to (CACHE_SIZE - Offset). It seems incredible that this bug wasn't found during testing or even on ITW documents just by chance. Nevertheless, by carefully constructing a powerpoint file with a series of records that massage the cache with a series of records, we can trigger a stack buffer overflow of attacker controlled data. The easiest way to do this is via PPFindRecSet in libdec2ss (this is part of ccScanw.dll on Windows). Early on when processing powerpoint documents Symantec attempt to find the last edit via RT_UserEditAtom, then extract a set of records for RT_List and RT_ExternalObjectList allowing us to massage the stream cache appropriately. Naturally, Symantec disable /GS on Windows and do not use -fstack-protector, making exploitation absolutely trivial. The attached document redirects execution to 0x41414141 reliably on Windows. 0:065> g (1074.a14): Access violation - code c0000005 (!!! second chance !!!) eax=00000000 ebx=000025a0 ecx=00000200 edx=000025a0 esi=0396e358 edi=00002524 eip=41414141 esp=056df558 ebp=00000000 iopl=0 nv up ei pl zr na pe nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246 41414141 ?? ??? 0:065> lmv m ccScanW start end module name 65820000 65a4f000 ccScanw (deferred) Image path: C:\Program Files (x86)\Norton Security\Engine\22.6.0.142\ccScanw.dll Image name: ccScanw.dll Timestamp: Tue Jan 26 13:51:55 2016 (56A7EA7B) CheckSum: 0022B3ED ImageSize: 0022F000 File version: 13.1.2.19 Product version: 13.1.2.19 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 1.0 App File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Symantec Corporation ProductName: Symantec Security Technologies InternalName: ccScan OriginalFilename: CCSCAN.DLL ProductVersion: 13.1.2.19 FileVersion: 13.1.2.19 FileDescription: Symantec Scan Engine LegalCopyright: Copyright (c) 2015 Symantec Corporation. All rights reserved. The fix is simply to round up requests to MIN(RequestSize, CACHE_SIZE). I verified this bug exists on the following products: * Norton Antivirus (All Platforms) * Symantec Endpoint (All Platforms) * Symantec Scan Engine (All Platforms) * Symantec Email Security (All Platforms) And probably all other Symantec and Norton branded products. NOTES: PPGetVBAEmbedListInfo() uses PPFindRecSet(), which is definitely the easiest way to exploit this. The prototype is something like: int PPFindRecSet(tagSS_STREAM *stream, unsigned StartOffset, unsigned EndOffset, short count, short *RequiredRecordTypes, unsigned *RecordOffsets, int *RecordLengths); Proof of Concept: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/40037.zip

Products Mentioned

Configuraton 0

Symantec>>Mail_security_for_microsoft_exchange >> Version From (including) 7.0 To (including) 7.0.4

Symantec>>Mail_security_for_microsoft_exchange >> Version From (including) 7.5 To (including) 7.5.4

Symantec>>Mail_security_for_microsoft_exchange >> Version 6.5.8

Configuraton 0

Symantec>>Norton_power_eraser >> Version To (including) 5.0

Configuraton 0

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

Symantec>>Protection_engine >> Version From (including) 7.5.0 To (including) 7.5.4

Symantec>>Protection_engine >> Version 7.8.0

Configuraton 0

Symantec>>Endpoint_protection >> Version 12.1.6

Symantec>>Endpoint_protection >> Version 12.1.6

Symantec>>Endpoint_protection >> Version 12.1.6

Symantec>>Endpoint_protection >> Version 12.1.6

Symantec>>Endpoint_protection >> Version 12.1.6

Configuraton 0

Symantec>>Message_gateway >> Version To (including) 10.6.1-3

Configuraton 0

Symantec>>Norton_360 >> Version *

Symantec>>Norton_antivirus >> Version *

Symantec>>Norton_internet_security >> Version *

Symantec>>Norton_security >> Version *

Symantec>>Norton_security_with_backup >> Version *

Symantec>>Ngc >> Version To (including) 22.6

Configuraton 0

Symantec>>Message_gateway_for_service_providers >> Version 10.5

Symantec>>Message_gateway_for_service_providers >> Version 10.6

Configuraton 0

Symantec>>Norton_bootable_removal_tool >> Version To (including) 2016.0

Configuraton 0

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

Symantec>>Mail_security_for_domino >> Version From (including) 8.1 To (including) 8.1.3

Configuraton 0

Symantec>>Data_center_security_server >> Version 6.0

Symantec>>Data_center_security_server >> Version 6.0

Symantec>>Data_center_security_server >> Version 6.5

Symantec>>Data_center_security_server >> Version 6.5

Symantec>>Data_center_security_server >> Version 6.6

Symantec>>Data_center_security_server >> Version 6.6

Configuraton 0

Symantec>>Norton_security >> Version To (including) 13.0.1

Configuraton 0

Symantec>>Advanced_threat_protection >> Version To (including) 2.0.3

Configuraton 0

Symantec>>Protection_for_sharepoint_servers >> Version 6.03

Symantec>>Protection_for_sharepoint_servers >> Version 6.04

Symantec>>Protection_for_sharepoint_servers >> Version 6.05

Symantec>>Protection_for_sharepoint_servers >> Version 6.06

Configuraton 0

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

Configuraton 0

Symantec>>Endpoint_protection >> Version 12.1.6

Symantec>>Endpoint_protection >> Version 12.1.6

Symantec>>Endpoint_protection >> Version 12.1.6

Symantec>>Endpoint_protection >> Version 12.1.6

Symantec>>Endpoint_protection >> Version 12.1.6

Apple>>Macos >> Version -

Linux>>Linux_kernel >> Version -

References

https://www.exploit-db.com/exploits/40037/
Tags : exploit, x_refsource_EXPLOIT-DB
http://www.securitytracker.com/id/1036199
Tags : vdb-entry, x_refsource_SECTRACK
http://www.securitytracker.com/id/1036198
Tags : vdb-entry, x_refsource_SECTRACK
http://www.securityfocus.com/bid/91436
Tags : vdb-entry, x_refsource_BID

Plus d'informations
Cliquez sur le bouton à gauche (OFF), pour autoriser l'inscription de cookie améliorant les fonctionnalités du site. Cliquez sur le bouton à gauche (Tout accepter), pour ne plus autoriser l'inscription de cookie améliorant les fonctionnalités du site.