froxlor up to 2.0.9 weak 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.
A vulnerability classified as problematic was found in froxlor up to 2.0.9. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a weak password vulnerability. The CWE definition for the vulnerability is CWE-521. The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts. As an impact it is known to affect confidentiality. The summary by CVE is:
Weak Password Requirements in GitHub repository froxlor/froxlor prior to 2.0.10.
The weakness was disclosed 01/29/2023. It is possible to read the advisory at huntr.dev. This vulnerability is known as CVE-2023-0564 since 01/29/2023. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
Upgrading to version 2.0.10 eliminates this vulnerability. Applying the patch 2a84e9c1207fd3d792b7fb198fd0c66fe1a66a7a is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
CVSSv3VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
CNA Base Score: 5.4
CNA Vector (huntr.dev): 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Weak password
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Upgrade: froxlor 2.0.10
Timeline01/29/2023 Advisory disclosed
01/29/2023 +0 days CVE reserved
01/29/2023 +0 days VulDB entry created
02/25/2023 +27 days VulDB last update
CVE: CVE-2023-0564 (🔒)
EntryCreated: 01/29/2023 08:45 AM
Updated: 02/25/2023 10:14 AM
Changes: 01/29/2023 08:45 AM (50), 02/25/2023 10:07 AM (1), 02/25/2023 10:14 AM (11)
Might our Artificial Intelligence support you?
Check our Alexa App!
No comments yet. Languages: en.
Please log in to comment.