1413 matches found
Design/Logic Flaw
When using wagtail-2fa before 1.3.0, if someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. This problem has been patched in version 1.3.0...
PYSEC-2019-65
When using wagtail-2fa before 1.3.0, if someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. This problem has been patched in version 1.3.0...
PYSEC-2019-135
When using wagtail-2fa before 1.3.0, if someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. This problem has been patched in version 1.3.0...
GHSA-89PX-WW3J-G2MM 2FA bypass in Wagtail through new device path
2FA bypass through new device path Impact If someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. Patches This problem has been patched in version 1.3.0...
2FA bypass in Wagtail through new device path
2FA bypass through new device path Impact If someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. Patches This problem has been patched in version 1.3.0...
CVE-2019-16766 2FA bypass in Wagtail through new device path
When using wagtail-2fa before 1.3.0, if someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. This problem has been patched in version 1.3.0...
CVE-2019-16766
Summary: CVE-2019-16766 affects the wagtail-2fa package prior to 1.3.0. If an attacker gains a user’s Wagtail credentials, they can bypass the two‑factor check by modifying the URL, then add a new device and gain full CMS access. The issue is resolved in version 1.3.0. Impact details (as describe...
CVE-2019-16766
When using wagtail-2fa before 1.3.0, if someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. This problem has been patched in version 1.3.0...
PT-2019-14822
Name of the Vulnerable Software and Affected Versions wagtail-2fa versions prior to 1.3.0 Description The issue allows an attacker to bypass the 2FA check by changing the URL after gaining access to someone's Wagtail login credentials. They can then add a new device and gain full access to the CM...
PT-2019-20152
Name of the Vulnerable Software and Affected Versions wagtail-2fa versions prior to 1.3.0 Description The issue allows an attacker to bypass the 2-factor authentication 2FA check in the Wagtail CMS by manipulating the URL, potentially gaining full access to the system if they have obtained a user...
CVE-2019-16766: Missing Critical Step in Authentication
When using wagtail-2fa before 1.3.0, if someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS. This problem has been patched in version 1.3.0...
Ginp Android trojan targets banking apps & threatens 2FA/SMS
By Waqas Dubbed Ginp; the trojan keeps coming back with new capabilities. Here's what the malware does to Android devices... This is a post from HackRead.com Read the original post: Ginp Android trojan targets banking apps & threatens 2FA/SMS...
Moneybird: Pending MFA logins aren't immediatly expired after a password change
Researcher found an issue with sessions not all being terminated when password is changed. The 2FA implementation was at fault in this scenario as the session was found to be active even after the password was changed and two-step verification was turned off...
Information Disclosure
pimcore/pimcore is vulnerable to information disclosure. The vulnerability exists through brute-force attacks for the 2FA token...
CVE-2019-18985
Pimcore before 6.2.2 lacks brute force protection for the 2FA token...
CVE-2019-18985
Pimcore before 6.2.2 lacks brute force protection for the 2FA token...
Design/Logic Flaw
Pimcore before 6.2.2 lacks brute force protection for the 2FA token...
CVE-2019-18985
Pimcore before 6.2.2 lacks brute force protection for the 2FA token...
CVE-2019-18985
CVE-2019-18985 affects Pimcore prior to version 6.2.2, where there is no brute-force protection for the 2FA token. The vulnerability arises from missing rate-limiting on 2FA attempts, enabling offline-like or automated brute force toward 2FA tokens, potentially allowing account compromise. The CV...