DaybydayCRM: Weak Password Requirements
CVE-2022-22110 is a high-severity weak password requirements vulnerability in DaybydayCRM from Bottelet, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected DaybydayCRM versions: 2.2.0 and earlier; 1.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.16% chance of exploitation within 30 days, higher than 68% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of DaybydayCRM 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
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Bottelet | DaybydayCRM | 2.2.0 and earlier; 1.1 | Not stated |
| Bottelet | flarepoint | 2.2.0 and earlier; 1.1 | Not stated |
| Daybydaycrm | Daybyday CRM | 1.1.0 through 2.2.0 | Not stated |
Version data comes from the organisation that assigned the CVE. 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
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (mend.io) |
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 2.0 | 5.0 | Medium | NVD |
Official description
In Daybyday CRM, versions 1.1 through 2.2.0 enforce weak password requirements in the user update functionality. A user with privileges to update his password could change it to a weak password, such as those with a length of a single character. This may allow an attacker to brute-force users’ passwords with minimal to no computational effort.
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.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/Bottelet/DaybydayCRM/commit/a0392f4a4a14e1e3fedaf6817aefce69b6bd661bThird Party Advisory
Third-party and government advisories
- whitesourcesoftware.com/vulnerability-database/CVE-2022-22110Third Party Advisory
Other vulnerabilities in DaybydayCRM
- 8.8 High severity
- 8.8 High severity
Recent Weak Password Requirements vulnerabilities
- 7.0 High severity
TeamViewer Desktop Bypass Remote Login Exploited
Spotted an error? Tell us.