Microsoft Lync 2010/2013 memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.7$0-$5k0.00

Summaryinfo

A vulnerability has been found in Microsoft Lync 2010/2013 and classified as problematic. This affects an unknown part. This manipulation causes memory corruption. This vulnerability is registered as CVE-2013-1302. Furthermore, an exploit is available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability has been found in Microsoft Lync 2010/2013 (Unified Communication Software) and classified as critical. Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Microsoft Communicator 2007 R2, Lync 2010, Lync 2010 Attendee, and Lync Server 2013 do not properly handle objects in memory, which allows remote attackers to execute arbitrary code via an invitation that triggers access to a deleted object, aka "Lync RCE Vulnerability."

The weakness was published 05/14/2013 with Microsoft as MS13-041 as confirmed bulletin (Microsoft Technet). The advisory is shared at technet.microsoft.com. The public release has been coordinated with Microsoft. This vulnerability is known as CVE-2013-1302 since 01/12/2013. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a private exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 66416 (MS13-041: Vulnerability in Lync Could Allow Remote Code Execution (2834695)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows : Microsoft Bulletins. The commercial vulnerability scanner Qualys is able to test this issue with plugin 90886 (Microsoft Lync Remote Code Execution Vulnerability (MS13-041)).

Applying the patch MS13-041 is able to eliminate this problem. The bugfix is ready for download at technet.microsoft.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (66416), OSVDB (93303†), Secunia (SA53363†) and Vulnerability Center (SBV-39588†). Additional details are provided at nakedsecurity.sophos.com. Similar entries are available at VDB-8711, VDB-8712, VDB-8713 and VDB-8714. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 8.7

VulDB Base Score: 10.0
VulDB Temp Score: 8.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Private
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 66416
Nessus Name: MS13-041: Vulnerability in Lync Could Allow Remote Code Execution (2834695)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 903308
OpenVAS Name: \Web Components\Autodiscover\Ext\Bin\microsoft.rtc.internal.autodiscover.dll
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Patch: MS13-041

Timelineinfo

01/12/2013 🔍
05/14/2013 +122 days 🔍
05/14/2013 +0 days 🔍
05/14/2013 +0 days 🔍
05/14/2013 +0 days 🔍
05/14/2013 +0 days 🔍
05/15/2013 +1 days 🔍
05/15/2013 +0 days 🔍
05/16/2013 +1 days 🔍
12/28/2024 +4243 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: MS13-041
Organization: Microsoft
Status: Confirmed
Coordinated: 🔍

CVE: CVE-2013-1302 (🔍)
GCVE (CVE): GCVE-0-2013-1302
GCVE (VulDB): GCVE-100-8725

OVAL: 🔍
IAVM: 🔍

Secunia: 53363 - Microsoft Lync / Office Communicator Use-After-Free Vulnerability, Less Critical
OSVDB: 93303
Vulnerability Center: 39588 - [MS13-041] Microsoft Communicator, Lync and Lync Server Remote Arbitrary Code Execution via an Invitation that Causes Access to a Deleted Object, Critical

scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
See also: 🔍

Entryinfo

Created: 05/15/2013 16:23
Updated: 12/28/2024 00:45
Changes: 05/15/2013 16:23 (82), 04/29/2017 23:08 (1), 05/11/2021 12:41 (2), 12/28/2024 00:45 (17)
Complete: 🔍
Committer:
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!