Ivanti Pulse Connect Secure up to 9.1R11 Push Configuration targets.cgi source 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.
2.6$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Ivanti Pulse Connect Secure up to 9.1R11. Affected by this vulnerability is an unknown functionality of the file targets.cgi of the component Push Configuration Handler. The manipulation leads to source code. This vulnerability is documented as CVE-2021-44720. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Ivanti Pulse Connect Secure up to 9.1R11 (Network Encryption Software). It has been rated as problematic. This issue affects some unknown processing of the file targets.cgi of the component Push Configuration Handler. The manipulation with an unknown input leads to a source code vulnerability. Using CWE to declare the problem leads to CWE-18. Impacted is confidentiality. The summary by CVE is:

In Ivanti Pulse Secure Pulse Connect Secure (PCS) before 9.1R12, the administrator password is stored in the HTML source code of the "Maintenance > Push Configuration > Targets > Target Name" targets.cgi screen. A read-only administrative user can escalate to a read-write administrative role.

The weakness was released 08/12/2022. The advisory is shared at gist.github.com. The identification of this vulnerability is CVE-2021-44720 since 12/08/2021. Technical details are known, but no exploit is available.

Upgrading to version 9.1R12 eliminates this vulnerability.

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

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.7
VulDB Meta Temp Score: 2.6

VulDB Base Score: 2.7
VulDB Temp Score: 2.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Source code
CWE: CWE-18 / CWE-17
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Pulse Connect Secure 9.1R12

Timelineinfo

12/08/2021 🔍
08/12/2022 +246 days 🔍
08/12/2022 +0 days 🔍
10/17/2022 +66 days 🔍

Sourcesinfo

Advisory: gist.github.com
Status: Confirmed

CVE: CVE-2021-44720 (🔍)
GCVE (CVE): GCVE-0-2021-44720
GCVE (VulDB): GCVE-100-206261

Entryinfo

Created: 08/12/2022 18:51
Updated: 10/17/2022 11:25
Changes: 08/12/2022 18:51 (40), 10/17/2022 11:25 (1)
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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!