bilde2910 Hauk 1.6.1 config.php 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.
5.5$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, was found in bilde2910 Hauk 1.6.1. This impacts an unknown function of the file config.php. The manipulation results in hard-coded password. This vulnerability is known as CVE-2022-37857. No exploit is available.

Detailsinfo

A vulnerability was found in bilde2910 Hauk 1.6.1. It has been classified as problematic. Affected is some unknown functionality of the file config.php. The manipulation with an unknown input leads to a hard-coded password vulnerability. CWE is classifying the issue as CWE-259. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. This is going to have an impact on confidentiality. CVE summarizes:

bilde2910 Hauk v1.6.1 requires a hardcoded password which by default is blank. This hardcoded password is hashed but stored within the config.php file server-side as well as in clear-text on the android client device by default.

The weakness was published 09/09/2022 as 187. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2022-37857 since 08/08/2022. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1078.001.

By approaching the search of inurl:config.php it is possible to find vulnerable targets with Google Hacking.

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

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

Name

Version

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.5

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

NVD Base Score: 7.5
NVD Vector: 🔍

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: Yes

Availability: 🔍
Status: Not defined
Google Hack: 🔍

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

08/08/2022 🔍
09/09/2022 +32 days 🔍
09/09/2022 +0 days 🔍
10/14/2022 +35 days 🔍

Sourcesinfo

Product: github.com

Advisory: 187
Status: Confirmed

CVE: CVE-2022-37857 (🔍)
GCVE (CVE): GCVE-0-2022-37857
GCVE (VulDB): GCVE-100-208140

Entryinfo

Created: 09/09/2022 07:24
Updated: 10/14/2022 15:19
Changes: 09/09/2022 07:24 (39), 10/14/2022 15:19 (11)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!