| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in froxlor up to 2.0.19. This affects an unknown function. Such manipulation leads to excessive authentication. This vulnerability is referenced as CVE-2023-3173. It is possible to launch the attack remotely. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, has been found in froxlor up to 2.0.19. Affected by this issue is an unknown function. The manipulation with an unknown input leads to a excessive authentication vulnerability. Using CWE to declare the problem leads to CWE-307. The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks. Impacted is confidentiality. CVE summarizes:
Improper Restriction of Excessive Authentication Attempts in GitHub repository froxlor/froxlor prior to 2.0.20.
The weakness was published 06/09/2023. The advisory is shared for download at huntr.dev. This vulnerability is handled as CVE-2023-3173 since 06/09/2023. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1110.001.
Upgrading to version 2.0.20 eliminates this vulnerability. Applying the patch 464216072456efb35b4541c58e7016463dfbd9a6 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 databases at EUVD (EUVD-2023-1776) and CERT Bund (WID-SEC-2026-1737). Once again VulDB remains the best source for vulnerability data.
Affected
- Open Source Froxlor
Product
Name
Version
- 2.0.0
- 2.0.1
- 2.0.2
- 2.0.3
- 2.0.4
- 2.0.5
- 2.0.6
- 2.0.7
- 2.0.8
- 2.0.9
- 2.0.10
- 2.0.11
- 2.0.12
- 2.0.13
- 2.0.14
- 2.0.15
- 2.0.16
- 2.0.17
- 2.0.18
- 2.0.19
License
Website
- Product: https://github.com/froxlor/froxlor/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 9.8
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: Excessive authenticationCWE: CWE-307 / CWE-799 / CWE-400
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.20
Patch: 464216072456efb35b4541c58e7016463dfbd9a6
Timeline
06/09/2023 🔍06/09/2023 🔍
06/09/2023 🔍
05/29/2026 🔍
Sources
Product: github.comAdvisory: 464216072456efb35b4541c58e7016463dfbd9a6
Status: Confirmed
CVE: CVE-2023-3173 (🔍)
GCVE (CVE): GCVE-0-2023-3173
GCVE (VulDB): GCVE-100-231140
EUVD: 🔍
CERT Bund: WID-SEC-2026-1737 - Froxlor: Mehrere Schwachstellen
Entry
Created: 06/09/2023 07:12Updated: 05/29/2026 13:42
Changes: 06/09/2023 07:12 (50), 07/07/2023 16:08 (1), 07/07/2023 16:15 (11), 07/16/2025 18:10 (16), 05/29/2026 13:42 (7)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.