CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.1 | $0-$5k | 0.00 |
A vulnerability, which was classified as critical, was found in DP3T-Backend-SDK up to 1.1.0. This affects an unknown code block of the component JWT Handler. The manipulation of the argument alg
with the input value none
leads to a signature verification vulnerability (DP3T). 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 summary by CVE is:
An issue was discovered in DP3T-Backend-SDK before 1.1.1 for Decentralised Privacy-Preserving Proximity Tracing (DP3T). When it is configured to check JWT before uploading/publishing keys, it is possible to skip the signature check by providing a JWT token with alg=none.
The weakness was presented 07/30/2020 (GitHub Repository). The advisory is shared at github.com. The public release was coordinated in cooperation with the project team. This vulnerability is uniquely identified as CVE-2020-15957 since 07/27/2020. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The advisory points out:
When dp3t-sdk-backend is configured to check a JWT before uploading/publishing keys, it was possible to skip the signature check by providing a JWT token with "alg":"none".
Upgrading to version 1.1.1 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Name: DP3TClass: Signature verification / DP3T
CWE: CWE-347 / CWE-345
ATT&CK: Unknown
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: DP3T-Backend-SDK 1.1.1
Timeline
07/27/2020 🔍07/30/2020 🔍
07/30/2020 🔍
07/31/2020 🔍
07/31/2020 🔍
Sources
Advisory: github.comStatus: Confirmed
Coordinated: 🔍
CVE: CVE-2020-15957 (🔍)
Entry
Created: 07/31/2020 06:33Updated: 07/31/2020 06:38
Changes: 07/31/2020 06:33 (47), 07/31/2020 06:38 (18)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.