phpMyFAQ versions 3.1.0 through 4.1.6 contain an authentication bypass vulnerability in AuthLdap::create(). When LDAP authentication is enabled, after a successful LDAP bind the code calls User::setStatus('active') unconditionally, which overwrites the account_status column of a pre-existing local account from 'blocked' to 'active'. As a result, a user whose local phpMyFAQ account has been administratively blocked can restore their account and log in by authenticating via LDAP. The state transition is not logged, so administrators cannot detect that the block was overridden. Fixed in 4.1.7.
oryginał ENCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XPhpmyfaq
APPPhpmyfaq3.1.0 – 4.1.6 (bez)
Powiązane podatności
phpMyFAQ before 4.1.7 fails to persist the WebAuthn login challenge generated by prepareForLogin, because neit...
phpMyFAQ before 4.1.7 contains a brute-force vulnerability in the two-factor authentication step where the fai...
Nieprawidłowe wygasanie sesji w phpMyFAQ przed wersją 3.2.2
phpMyFAQ — nieograniczony upload niebezpiecznych plików (RCE)
CSV Injection w phpMyFAQ — wstrzyknięcie formuł do pliku CSV