Pan OsOperating system · Paloaltonetworks
CVE-2017-17841
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 · uneditedPalo Alto Networks PAN-OS 6.1, 7.1, and 8.0.x before 8.0.7, when an interface implements SSL decryption with RSA enabled or hosts a GlobalProtect portal or gateway, might allow remote attackers to decrypt TLS ciphertext data by leveraging a Bleichenbacher RSA padding oracle, aka a ROBOT attack.
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 is a Bleichenbacher RSA padding oracle (ROBOT attack) vulnerability in Palo Alto Networks PAN-OS. When an interface implements SSL decryption with RSA key exchange enabled or hosts a GlobalProtect portal/gateway, the device's responses to malformed RSA padding in TLS handshakes leak timing or other side-channel information that allows remote attackers to gradually decrypt TLS ciphertext data.
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
Pan OsOperating system
= 6.1.0= 7.1.0= 7.1.1= 7.1.2= 7.1.3= 7.1.4= 7.1.4-h2= 7.1.5= 7.1.6= 7.1.7= 7.1.8= 7.1.9CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check PAN-OS versionAccess the device dashboard or run 'show system info' in the CLI to display the installed PAN-OS versionAffected if The version matches 6.1.0 or any 7.1.x version from 7.1.0 through 7.1.9 (including 7.1.4-h2)
-
Identify SSL decryption profilesNavigate to Objects > SSL Decryption in the management interface or run 'show ssl-decryption' in the CLI to list all SSL decryption profilesAffected if Any SSL decryption profile exists and is applied to traffic interfaces
-
Verify RSA key exchange is enabled in SSL decryptionOpen each SSL decryption profile and inspect the 'RSA Key Exchange' setting under the forward proxy or inbound inspection rulesAffected if RSA key exchange is enabled (not disabled) in any active SSL decryption profile applied to traffic
-
Identify GlobalProtect configurationsNavigate to Network > GlobalProtect or run 'show global-protector' in the CLI to list configured GlobalProtect portals and gatewaysAffected if A GlobalProtect portal or gateway is enabled on any interface
A system is affected if it runs PAN-OS 6.1.0 or 7.1.0-7.1.9 and has either an active SSL decryption profile with RSA key exchange enabled, or an enabled GlobalProtect portal/gateway on any interface.
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 dataUpgrade PAN-OS to version 8.0.7 or later, or alternatively disable RSA key exchange in SSL decryption profiles and GlobalProtect configurations if upgrading is not immediately feasible.
Fix this in Pan Os
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17841 — 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-17841 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