jsrsasign Package up to 10.1.13 on node.js RSA PKCS#1 v1.5 Signature Verification 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. |
---|---|---|
4.6 | $0-$5k | 0.47 |
A vulnerability was found in jsrsasign Package up to 10.1.13 on node.js (JavaScript Library) and classified as problematic. Affected by this issue is an unknown part of the component RSA PKCS#1 v1.5 Signature Verification Handler. The manipulation with an unknown input leads to a weak authentication vulnerability. Using CWE to declare the problem leads to CWE-347. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In the jsrsasign package through 10.1.13 for Node.js, some invalid RSA PKCS#1 v1.5 signatures are mistakenly recognized to be valid. NOTE: there is no known practical attack.
The weakness was released 04/08/2021. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2021-30246 since 04/07/2021. The exploitation is known to be difficult. The attack needs to be done within the local network. A simple authentication is necessary for exploitation. There are neither technical details nor an exploit publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.6
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
🔍 | 🔍 | 🔍 | 🔍 | 🔍 | 🔍 |
🔍 | 🔍 | 🔍 | 🔍 | 🔍 | 🔍 |
🔍 | 🔍 | 🔍 | 🔍 | 🔍 | 🔍 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Weak authenticationCWE: CWE-347
ATT&CK: Unknown
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Threat: 🔍Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/07/2021 CVE assigned04/08/2021 Advisory disclosed
04/08/2021 VulDB entry created
04/11/2021 VulDB last update
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2021-30246 (🔒)
Entry
Created: 04/08/2021 09:59 AMUpdated: 04/11/2021 05:23 PM
Changes: (2) source_cve_assigned source_cve_nvd_summary
Complete: 🔍
Comments
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!
No comments yet. Please log in to comment.