Raspberry Pi OS up to 5.10 hard-coded password

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.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Raspberry Pi OS up to 5.10. This issue affects some unknown processing. This manipulation causes hard-coded password. This vulnerability is handled as CVE-2021-38759. Additionally, an exploit exists. It is suggested to update the configuration settings.

Detailsinfo

A vulnerability classified as critical was found in Raspberry Pi OS up to 5.10. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a hard-coded password vulnerability. The CWE definition for the vulnerability is CWE-259. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was released 12/08/2021 as CNVD-2021-43968. The advisory is shared at cnvd.org.cn. This vulnerability is known as CVE-2021-38759 since 08/16/2021. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1078.001 for this issue.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.

It is possible to mitigate the problem by applying the configuration setting .

The vulnerability is also documented in the vulnerability database at Exploit-DB (50576). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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

VulDB Base Score: 8.8
VulDB Temp Score: 8.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Hard-coded password
CWE: CWE-259 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Config
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/16/2021 🔍
12/08/2021 +114 days 🔍
12/08/2021 +0 days 🔍
09/24/2024 +1021 days 🔍

Sourcesinfo

Advisory: CNVD-2021-43968
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-38759 (🔍)
GCVE (CVE): GCVE-0-2021-38759
GCVE (VulDB): GCVE-100-187741
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 12/08/2021 09:30
Updated: 09/24/2024 13:50
Changes: 12/08/2021 09:30 (39), 12/11/2021 06:39 (1), 09/24/2024 13:50 (23)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!