Pulse Secure Desktop on Windows access control

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.
7.6$0-$5k0.00

A vulnerability was found in Pulse Secure Desktop on Windows (the affected version is unknown). It has been classified as critical. Affected is an unknown code. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was disclosed 07/24/2016 by Zhipeng Huo with Tencent as SA40241 as confirmed security advisory (Website). The advisory is available at kb.pulsesecure.net. This vulnerability is traded as CVE-2016-2408 since 02/18/2016. The exploitability is told to be easy. Local access is required to approach this attack. A authentication is needed for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1068 by the MITRE ATT&CK project.

The commercial vulnerability scanner Qualys is able to test this issue with plugin 371681 (Pulse Client Privilege Escalation Vulnerability (SA40241)).

Applying the patch 5.0r15.1/5.1r9.1/5.2r4.1 is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at SecurityFocus (BID 92692†) and SecurityTracker (ID 1036474†). The entries VDB-52788, VDB-55045, VDB-56629 and VDB-56637 are pretty similar.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB CVSS-B Score: 🔍
VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.8
VulDB Meta Temp Score: 7.6

VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

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

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

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

Patch: 5.0r15.1/5.1r9.1/5.2r4.1

Timelineinfo

02/18/2016 🔍
07/24/2016 +157 days 🔍
07/24/2016 +0 days 🔍
07/28/2016 +4 days 🔍
08/01/2016 +4 days 🔍
08/02/2016 +1 days 🔍
08/31/2016 +29 days 🔍
09/09/2022 +2200 days 🔍

Sourcesinfo

Advisory: SA40241
Researcher: Zhipeng Huo
Organization: Tencent
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-2408 (🔍)
SecurityFocus: 92692 - Multiple Pulse Secure Products CVE-2016-2408 Local Privilege Escalation Vulnerability
SecurityTracker: 1036474

See also: 🔍

Entryinfo

Created: 08/01/2016 01:21 PM
Updated: 09/09/2022 03:42 PM
Changes: 08/01/2016 01:21 PM (59), 03/15/2019 08:25 AM (13), 09/09/2022 03:42 PM (3)
Complete: 🔍
Cache ID: 44:F2C:40

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!