| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in froxlor up to 2.0.9 and classified as problematic. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in error condition. This vulnerability is reported as CVE-2023-0572. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in froxlor up to 2.0.9. This affects an unknown part. The manipulation with an unknown input leads to a error condition vulnerability. CWE is classifying the issue as CWE-391. [PLANNED FOR DEPRECATION. SEE MAINTENANCE NOTES AND CONSIDER CWE-252, CWE-248, OR CWE-1069.] Ignoring exceptions and other error conditions may allow an attacker to induce unexpected behavior unnoticed. This is going to have an impact on confidentiality. The summary by CVE is:
Unchecked Error Condition in GitHub repository froxlor/froxlor prior to 2.0.10.
The weakness was disclosed 01/30/2023. It is possible to read the advisory at huntr.dev. This vulnerability is uniquely identified as CVE-2023-0572 since 01/29/2023. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 2.0.10 eliminates this vulnerability. Applying the patch 7b08a71c59430d06c1efb012a6c6448262aacdb1 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-0316). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
License
Website
- Product: https://github.com/froxlor/froxlor/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (huntr.dev): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Error conditionCWE: CWE-391
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: froxlor 2.0.10
Patch: 7b08a71c59430d06c1efb012a6c6448262aacdb1
Timeline
01/29/2023 🔍01/30/2023 🔍
01/30/2023 🔍
07/02/2025 🔍
Sources
Product: github.comAdvisory: 7b08a71c59430d06c1efb012a6c6448262aacdb1
Status: Confirmed
CVE: CVE-2023-0572 (🔍)
GCVE (CVE): GCVE-0-2023-0572
GCVE (VulDB): GCVE-100-219747
EUVD: 🔍
Entry
Created: 01/30/2023 11:53Updated: 07/02/2025 15:42
Changes: 01/30/2023 11:53 (39), 02/25/2023 12:43 (1), 02/25/2023 12:50 (20), 07/02/2025 15:42 (16)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.