BTCPay Server up to 1.0.7.0 missing secure attribute

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

Summaryinfo

A vulnerability was found in BTCPay Server up to 1.0.7.0. It has been classified as problematic. This affects an unknown part. The manipulation leads to missing secure attribute. This vulnerability is listed as CVE-2021-29248. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in BTCPay Server up to 1.0.7.0. It has been rated as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a missing secure attribute vulnerability. Using CWE to declare the problem leads to CWE-614. The Secure attribute for sensitive cookies in HTTPS sessions is not set, which could cause the user agent to send those cookies in plaintext over an HTTP session. Impacted is confidentiality.

The weakness was presented 05/05/2021. The advisory is shared at blog.btcpayserver.org. The identification of this vulnerability is CVE-2021-29248. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1539 for this issue.

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

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

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.7
VulDB Meta Temp Score: 3.7

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

CVSSv2info

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

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

Exploitinginfo

Class: Missing secure attribute
CWE: CWE-614 / CWE-1004 / CWE-732
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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/26/2021 🔍
05/05/2021 +39 days 🔍
05/05/2021 +0 days 🔍
05/07/2021 +2 days 🔍

Sourcesinfo

Advisory: blog.btcpayserver.org
Status: Confirmed

CVE: CVE-2021-29248 (🔍)
GCVE (CVE): GCVE-0-2021-29248
GCVE (VulDB): GCVE-100-174473

Entryinfo

Created: 05/05/2021 20:49
Updated: 05/07/2021 17:16
Changes: 05/05/2021 20:49 (35), 05/07/2021 17:16 (2)
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!