Juniper Pulse Secure PSA5000/Pulse Secure PSA7000 BIOS Firmware malicious code

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.
5.2$5k-$25k0.00

Summaryinfo

A vulnerability was found in Juniper Pulse Secure PSA5000 and Pulse Secure PSA7000. It has been rated as critical. Affected by this vulnerability is an unknown functionality of the component BIOS Firmware Handler. This manipulation causes an unknown weakness. This vulnerability is registered as CVE-2021-22887. No exploit is available.

Detailsinfo

A vulnerability classified as critical was found in Juniper Pulse Secure PSA5000 and Pulse Secure PSA7000 (version unknown). Affected by this vulnerability is an unknown function of the component BIOS Firmware Handler. The CWE definition for the vulnerability is CWE-506. The product contains code that appears to be malicious in nature. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was published 03/17/2021. The advisory is shared at kb.pulsesecure.net. This vulnerability is known as CVE-2021-22887. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 04/01/2021).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

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

Productinfo

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.2
VulDB Meta Temp Score: 5.2

VulDB Base Score: 8.0
VulDB Temp Score: 8.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 2.3
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Malicious code
CWE: CWE-506
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/06/2021 🔍
03/17/2021 +70 days 🔍
03/17/2021 +0 days 🔍
04/01/2021 +15 days 🔍

Sourcesinfo

Vendor: juniper.net

Advisory: kb.pulsesecure.net
Status: Confirmed

CVE: CVE-2021-22887 (🔍)
GCVE (CVE): GCVE-0-2021-22887
GCVE (VulDB): GCVE-100-171325

Entryinfo

Created: 03/17/2021 09:11
Updated: 04/01/2021 23:03
Changes: 03/17/2021 09:11 (33), 04/01/2021 22:56 (2), 04/01/2021 23:03 (19)
Complete: 🔍
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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!