CVE-2017-18462
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 · uneditedcPanel before 62.0.17 allows a CPHulk one-day ban bypass when IP based protection is enabled (SEC-224).
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 · high confidenceThis vulnerability in cPanel before 62.0.17 allows attackers to bypass CPHulk's IP-based ban mechanism. CPHulk is cPanel's brute-force protection system that bans IPs after failed login attempts. The bypass enables attackers to evade the one-day ban duration that would normally be applied, potentially allowing continued brute-force attempts against authentication mechanisms.
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>= 55.9999.61, < 56.0.46>= 57.9999.48, < 58.0.45>= 59.9999.58, < 60.0.39>= 61.9999.55, < 62.0.17CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check cPanel versionRun `/usr/local/cpanel/cpanel -V` or `cat /usr/local/cpanel/version` to obtain the installed cPanel version numberAffected if The version falls within any of these ranges: 55.9999.61 to 56.0.45, 57.9999.48 to 58.0.44, 59.9999.58 to 60.0.38, or 61.9999.55 to 62.0.16
-
Verify CPHulk is enabledCheck CPHulk status via WHM at Security Center > cPHulk Brute Force Protection, or run `/usr/local/cpanel/bin/cphulk_pfctl -status` from command lineAffected if CPHulk is actively enabled on the server - the bypass only affects environments where CPHulk's brute-force protection is in use
-
Confirm ban mechanism configurationReview CPHulk settings in WHM to confirm ban duration is set (default is one day). Check if the 'Enable Brute Force Detection' option is turned ONAffected if CPHulk is configured with IP banning enabled and the version is vulnerable, the environment is susceptible to the bypass
If the installed cPanel version is within the affected ranges AND CPHulk is enabled, the environment is vulnerable to CVE-2017-18462 and attackers can evade IP bans.
Generated from the published advisory. Verify against your own configuration.
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 data56.0.4658.0.4560.0.39
Update cPanel to version 62.0.17 or later to patch this vulnerability. In the interim, implement additional network-level access controls or rate-limiting to mitigate the risk of brute-force attacks.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18462 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-18462 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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