PySAML2 up to 6.4.x CryptoBackendXmlSec1 Backend xmlsec1 signature verification

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

Summaryinfo

A vulnerability was found in PySAML2 up to 6.4.x. It has been rated as problematic. Affected by this issue is some unknown functionality of the file xmlsec1 of the component CryptoBackendXmlSec1 Backend. Performing a manipulation results in signature verification. This vulnerability is cataloged as CVE-2021-21239. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, was found in PySAML2 up to 6.4.x. This affects an unknown function of the file xmlsec1 of the component CryptoBackendXmlSec1 Backend. The manipulation with an unknown input leads to a signature verification vulnerability. CWE is classifying the issue as CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. This is going to have an impact on integrity.

The weakness was shared 01/22/2021. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2021-21239. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

Upgrading to version 6.5.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.1
VulDB Meta Temp Score: 3.0

VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Signature verification
CWE: CWE-347 / CWE-345
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: PySAML2 6.5.0
Patch: github.com

Timelineinfo

12/22/2020 🔍
01/22/2021 +31 days 🔍
01/22/2021 +0 days 🔍
02/19/2021 +28 days 🔍

Sourcesinfo

Advisory: github.com
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-21239 (🔍)
GCVE (CVE): GCVE-0-2021-21239
GCVE (VulDB): GCVE-100-168609

Entryinfo

Created: 01/22/2021 08:01
Updated: 02/19/2021 11:01
Changes: 01/22/2021 08:01 (40), 02/19/2021 10:54 (6), 02/19/2021 11:01 (8)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!