Apache Superset up to 2.0.1 SECRET_KEY insecure default initialization of resource

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

Summaryinfo

A vulnerability, which was classified as critical, was found in Apache Superset up to 2.0.1. This affects an unknown part. Such manipulation of the argument SECRET_KEY leads to insecure default initialization of resource. This vulnerability is documented as CVE-2023-27524. The attack can be executed remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Apache Superset up to 2.0.1. Affected by this issue is some unknown functionality. The manipulation of the argument SECRET_KEY with an unknown input leads to a insecure default initialization of resource vulnerability. Using CWE to declare the problem leads to CWE-1188. The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure. Impacted is confidentiality, integrity, and availability. CVE summarizes:

Session Validation attacks in Apache Superset versions up to and including 2.0.1. Installations that have not altered the default configured SECRET_KEY according to installation instructions allow for an attacker to authenticate and access unauthorized resources. This does not affect Superset administrators who have changed the default value for SECRET_KEY config. All superset installations should always set a unique secure random SECRET_KEY. Your SECRET_KEY is used to securely sign all session cookies and encrypting sensitive information on the database. Add a strong SECRET_KEY to your `superset_config.py` file like: SECRET_KEY = <YOUR_OWN_RANDOM_GENERATED_SECRET_KEY> Alternatively you can set it with `SUPERSET_SECRET_KEY` environment variable.

The weakness was released 04/24/2023. The advisory is available at lists.apache.org. This vulnerability is handled as CVE-2023-27524 since 03/02/2023. Technical details as well as a public exploit are known.

The exploit is available at exploit-db.com. It is declared as attacked. As 0-day the estimated underground price was around $5k-$25k. This issue was added on 01/08/2024 to the CISA Known Exploited Vulnerabilities Catalog with a due date of 01/29/2024:

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

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

The vulnerability is also documented in the vulnerability database at Exploit-DB (51447). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.1
VulDB Meta Temp Score: 8.1

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

NVD Base Score: 9.8
NVD Vector: 🔍

CNA Base Score: 8.9
CNA Vector (Apache Software Foundation): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Insecure default initialization of resource
CWE: CWE-1188
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Attacked
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

KEV Added: 🔍
KEV Due: 🔍
KEV Remediation: 🔍
KEV Ransomware: 🔍
KEV Notice: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/02/2023 🔍
04/24/2023 +52 days 🔍
04/24/2023 +0 days 🔍
02/25/2026 +1038 days 🔍

Sourcesinfo

Vendor: apache.org

Advisory: lists.apache.org
Status: Confirmed

CVE: CVE-2023-27524 (🔍)
GCVE (CVE): GCVE-0-2023-27524
GCVE (VulDB): GCVE-100-227306
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 04/24/2023 20:33
Updated: 02/25/2026 23:52
Changes: 04/24/2023 20:33 (46), 05/18/2023 13:11 (12), 04/30/2024 10:00 (26), 08/15/2024 05:07 (4), 09/29/2024 04:24 (1), 02/25/2026 23:52 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!