dbcve.org
PanelApplication · Pterodactyl

CVE-2019-1020002

HIGH · 7.5 CVSS v3.0 Published 2019-07-29
Fix available
A fix is available. Upgrade to 0.7.14 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Pterodactyl before 0.7.14 with 2FA allows credential sniffing.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Pterodactyl versions prior to 0.7.14 contain a vulnerability in their two-factor authentication (2FA) implementation that allows attackers to sniff or intercept credentials during the authentication process, potentially exposing user credentials or 2FA secrets.

MitigationUpgrade Pterodactyl to version 0.7.14 or later to remediate the 2FA credential-sniffing vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PanelApplication
Affected:< 0.7.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate your Pterodactyl Panel version
    Access the admin area of your Pterodactyl Panel and navigate to the version information page, or check the version file in your installation directory
    Affected if the displayed version number is lower than 0.7.14
  2. Verify 2FA is in use
    Check if any user accounts on the Panel have two-factor authentication enabled in their account settings
    Affected if 2FA is enabled for any user account on the Panel
  3. Compare installed version to affected range
    Confirm that your Pterodactyl Panel version is less than 0.7.14
    Affected if the installed version is below 0.7.14 and 2FA is in use on the Panel

Your environment is affected if the Pterodactyl Panel version is below 0.7.14 and two-factor authentication is enabled for any user account.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 0.7.14 or later
Fixed in 0.7.14
Interim mitigation

Upgrade Pterodactyl to version 0.7.14 or later to remediate the 2FA credential-sniffing vulnerability.

Fix this in Panel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1020002 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1020002 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data