froxlor up to 2.0.9 logic error

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in froxlor up to 2.0.9. This impacts an unknown function. This manipulation causes logic error. This vulnerability is registered as CVE-2023-0565. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in froxlor up to 2.0.9. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a logic error vulnerability. The CWE definition for the vulnerability is CWE-840. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Business Logic Errors in GitHub repository froxlor/froxlor prior to 2.0.10.

The weakness was published 01/30/2023. The advisory is shared at huntr.dev. This vulnerability is known as CVE-2023-0565 since 01/29/2023. Neither technical details nor an exploit are publicly available.

Upgrading to version 2.0.10 eliminates this vulnerability. Applying the patch 2feb8020941a82bfb4ac68890f6ced0e5b3c4a15 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.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-0564). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 5.0

VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 4.9
NVD Vector: 🔍

CNA Base Score: 5.5
CNA Vector (huntr.dev): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Logic error
CWE: CWE-840
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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: froxlor 2.0.10
Patch: 2feb8020941a82bfb4ac68890f6ced0e5b3c4a15

Timelineinfo

01/29/2023 🔍
01/30/2023 +1 days 🔍
01/30/2023 +0 days 🔍
07/05/2025 +887 days 🔍

Sourcesinfo

Product: github.com

Advisory: 2feb8020941a82bfb4ac68890f6ced0e5b3c4a15
Status: Confirmed

CVE: CVE-2023-0565 (🔍)
GCVE (CVE): GCVE-0-2023-0565
GCVE (VulDB): GCVE-100-219745
EUVD: 🔍

Entryinfo

Created: 01/30/2023 11:53
Updated: 07/05/2025 13:44
Changes: 01/30/2023 11:53 (49), 02/25/2023 12:14 (1), 02/25/2023 12:21 (10), 07/05/2025 13:44 (15)
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 stay up to date on a daily basis?

Enable the mail alert feature now!