CVE-2024-34340: Authentication Bypass when using using older password hashes
Cacti provides an operational monitoring and fault management framework. Prior to version 1.2.27, Cacti calls compatpasswordhash when users set their password. compatpasswordhash use passwordhash if there is it, else use md5. When verifying password, it calls compatpasswordverify. In compatpasswordverify, passwordverify is called if there is it, else use md5. passwordverify and passwordhash are supported on PHP < 5.5.0, following PHP manual. The vulnerability is in compatpasswordverify. Md5-hashed user input is compared with correct password in database by $md5 == $hash. It is a loose comparison, not ===. It is a type juggling vulnerability. Version 1.2.27 contains a patch for the issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/cactito a version that resolves this vulnerability.Fixed in 1.2.24+ds1-1+deb12u3 - Upgrade
Upgrade
debian/cactito a version that resolves this vulnerability.Fixed in 1.2.27+ds1-1 - Upgrade
Upgrade
debian/cactito a version that resolves this vulnerability.Fixed in 1.2.24+ds1-1+deb12u5Fixed in 1.2.30+ds1-1Fixed in 1.2.31+ds1-4 - Upgrade
Upgrade
alpine/cactito a version that resolves this vulnerability.Fixed in 1.2.27-r0 - Upgrade
Upgrade
Cactito a version that resolves this vulnerability.Fixed in 1.2.27
Event History
Frequently Asked Questions
What is the severity of CVE-2024-34340?
CVE-2024-34340 is considered a medium severity vulnerability due to improper password hashing.
How do I fix CVE-2024-34340?
To fix CVE-2024-34340, upgrade your Cacti installation to version 1.2.27 or later.
Which versions of Cacti are affected by CVE-2024-34340?
CVE-2024-34340 affects Cacti versions prior to 1.2.27.
What is the impact of CVE-2024-34340 on user accounts?
The impact of CVE-2024-34340 could allow attackers to potentially compromise user accounts due to insufficient password hashing.
Is there a workaround for CVE-2024-34340 before applying a patch?
There is no official workaround specified for CVE-2024-34340, so upgrading is the recommended action.