CVE-2019-1020002
published 2019-07-29CVE-2019-1020002: Pterodactyl before 0.7.14 with 2FA allows credential sniffing.
PriorityP339high7.5CVSS 3.0
AVNACLPRNUINSUCHINAN
EPSS
1.47%
70.6th percentile
Pterodactyl before 0.7.14 with 2FA allows credential sniffing.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| pterodactyl | panel | < 0.7.14 | 0.7.14 |
| pterodactyl | panel | >= 0 < 0.7.14 | 0.7.14 |
| pterodactyl | pterodactyl_panel | < 0.7.14 | 0.7.14 |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Pterodactyl vulnerable to 2FA Sniffing
ghsa·2022-05-24
CVE-2019-1020002 [HIGH] CWE-203 Pterodactyl vulnerable to 2FA Sniffing
Pterodactyl vulnerable to 2FA Sniffing
**Pterodactyl version 0.7.13 and lower - 2FA Sniffing**
Users who have enabled 2FA protections on their account can unintentionally have their account's existence sniffed by malicious users who enter random credentials into the login fields.
### Impact
Users who have enabled 2FA protections on their account can unintentionally have their account's existence sniffed by malicious users who enter random credentials into the login fields.
A logical mistake was made when the original code was written that would wait to verify the user's password until they had provided 2FA credentials if it was enabled on their account. However, because of this you could enter a bad password for a known email and determine if the account exists if you got redirected to
OSV
Pterodactyl vulnerable to 2FA Sniffing
osv·2022-05-24
CVE-2019-1020002 [HIGH] Pterodactyl vulnerable to 2FA Sniffing
Pterodactyl vulnerable to 2FA Sniffing
**Pterodactyl version 0.7.13 and lower - 2FA Sniffing**
Users who have enabled 2FA protections on their account can unintentionally have their account's existence sniffed by malicious users who enter random credentials into the login fields.
### Impact
Users who have enabled 2FA protections on their account can unintentionally have their account's existence sniffed by malicious users who enter random credentials into the login fields.
A logical mistake was made when the original code was written that would wait to verify the user's password until they had provided 2FA credentials if it was enabled on their account. However, because of this you could enter a bad password for a known email and determine if the account exists if you got redirected to
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2019-07-29
Published