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.
Advisories
Source ID Title
EUVD EUVD EUVD-2022-0541 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.
Github GHSA Github GHSA GHSA-96v6-hrwg-p378 Weak Password Requirements in Daybyday CRM
Fixes

Solution

Update to 2.2.1


Workaround

No workaround given by the vendor.

History

No history.

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: Mend

Published:

Updated: 2024-08-03T03:00:55.381Z

Reserved: 2021-12-21T00:00:00

Link: CVE-2022-22110

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2022-01-05T15:15:07.923

Modified: 2024-11-21T06:46:12.150

Link: CVE-2022-22110

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses