Weak directory passwords via skipped policy validation
Published Jan 29, 2023 · Updated Mar 28, 2025
Weak password enforcement in Froxlor before 2.0.10 allows remote authenticated users to set policy-noncompliant directory passwords. The DirProtections API add and update methods checked only that a password was present, without passing it to Crypt::validatePassword for configured strength validation. Any authenticated account allowed to manage directory protection can assign a weak HTTP authentication password, increasing protected-content exposure to password guessing.
Summary
What happened
Weak password enforcement in Froxlor before 2.0.10 allows remote authenticated users to set policy-noncompliant directory passwords. The DirProtections API add and update methods checked only that a password was present, without passing it to Crypt::validatePassword for configured strength validation. Any authenticated account allowed to manage directory protection can assign a weak HTTP authentication password, increasing protected-content exposure to password guessing.
The record
- CVE
- CVE-2023-0564
- Published
- Jan 29, 2023
- Updated
- Mar 28, 2025
- Vendor
- Froxlor
- Product
- Froxlor
- Classifications
- CWE-521, T1110.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 29, 2023CVE publishedPublication date reported by the CVE source.
- Mar 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <2.0.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- huntr.dev proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo