CVE-2024-2550
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 · uneditedA null pointer dereference vulnerability in the GlobalProtect gateway in Palo Alto Networks PAN-OS software enables an unauthenticated attacker to stop the GlobalProtect service on the firewall by sending a specially crafted packet that causes a denial of service (DoS) condition. Repeated attempts to trigger this condition result in the firewall entering maintenance mode.
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 confidenceA null pointer dereference vulnerability in the GlobalProtect gateway in PAN-OS allows unauthenticated attackers to send specially crafted packets that crash the GlobalProtect service, causing denial of service. Repeated exploitation forces the firewall into maintenance mode.
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>= 10.2.0, < 10.2.7>= 11.0.0, < 11.0.6>= 11.1.0, < 11.1.4= 10.2.7= 10.2.8= 10.2.9= 10.2.10= 11.1.4CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify installed PAN-OS versionRun 'show system info' or access the firewall web interface under Device > Setup > Operations to view the PAN-OS version numberAffected if The installed version falls within 10.2.0-10.2.10, 11.0.0-11.0.5, or 11.1.0-11.1.4
-
Confirm GlobalProtect gateway is enabledNavigate to Network > GlobalProtect > Gateways or run 'show global-protect gateway' in the CLI to list active gatewaysAffected if At least one GlobalProtect gateway is configured and enabled on the firewall
-
Verify GlobalProtect service accessibilityCheck the interface and zone assignment for GlobalProtect gateways under Network > GlobalProtect > Gateways, and review external interface exposure using 'show interface' or the web interfaceAffected if The GlobalProtect gateway is reachable from untrusted or external networks (such as the internet or untrusted zones)
A system is affected if it runs a vulnerable PAN-OS version (10.2.0-10.2.10, 11.0.0-11.0.5, or 11.1.0-11.1.4) AND has a GlobalProtect gateway enabled and accessible to unauthenticated attackers.
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.
dbcve · scoped10.2.711.0.611.1.4
Apply the vendor-provided PAN-OS patch for CVE-2024-2550; until patched, consider restricting GlobalProtect gateway access to trusted sources or implementing additional network-level controls.
PAN-OS 10.2.7-h2 or later (10.2.x branch); PAN-OS 11.0.6-h2 or later (11.0.x branch); PAN-OS 11.1.4-h2 or later (11.1.x branch)
- 1. Identify the current PAN-OS version running on the firewall by navigating to Device > Dynamic Updates in the web interface or using 'show system info' in the CLI
- 2. Based on the current version branch, determine the minimum fixed release: for 10.2.x upgrade to 10.2.7-h2 or later; for 11.0.x upgrade to 11.0.6-h2 or later; for 11.1.x upgrade to 11.1.4-h2 or later
- 3. Download the recommended PAN-OS upgrade file from the Palo Alto Networks Customer Support Portal
- 4. Before upgrading, backup the firewall configuration via Device > Setup > Operations > Save Config Named Version
- 5. Upload the PAN-OS upgrade file via Device > Software > Upload
- 6. Install the upgrade: Device > Software > Install and select the uploaded version
- 7. After installation, reboot the firewall to load the new version
- 8. Verify the upgrade was successful and the GlobalProtect service is running normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2550 — 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-2024-2550 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