I-doit: Weak Password Requirements
CVE-2023-37756 is a critical-severity weak password requirements vulnerability in I-doit, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected I-doit versions: 25 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.45% chance of exploitation within 30 days, higher than 74% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of I-doit you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
Official description
I-doit pro 25 and below and I-doit open 25 and below employ weak password requirements for Administrator account creation. Attackers are able to easily guess users' passwords via a bruteforce attack.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Weak Password Requirements
The product does not require that users should have strong passwords.
How developers prevent this class of flaw
- Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. See CWE-308 for further information.
- Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- github.com/leekenghwa/CVE-2023-37756-CWE-521-lead-to-malicious-plugin-upload-in-the-i-doit-Pro-25-and-below/b…Exploit, Third Party Advisory
Other references
Other vulnerabilities in I-doit
- 7.5 High severity
- 9.8 Critical severity
Recent Weak Password Requirements vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.