CVE-2024-3382
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 memory leak exists in Palo Alto Networks PAN-OS software that enables an attacker to send a burst of crafted packets through the firewall that eventually prevents the firewall from processing traffic. This issue applies only to PA-5400 Series devices that are running PAN-OS software with the SSL Forward Proxy feature enabled.
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 confidenceA memory leak vulnerability in PAN-OS on PA-5400 Series devices allows remote attackers to send crafted packets through the firewall. When SSL Forward Proxy is enabled, these packets trigger a memory leak that eventually exhausts resources and prevents the firewall from processing legitimate traffic, causing denial of service.
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.4>= 11.1.0, < 11.1.2= 10.2.7CVSS 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 device modelAccess the firewall CLI and run 'show system info' or check the web interface Dashboard to confirm the device model is PA-5400 Series.Affected if Device is not a PA-5400 Series device (other models are not affected by this specific CVE)
-
Check PAN-OS versionRun 'show system info' in the CLI or view the Dashboard in the web interface to find the installed PAN-OS version number.Affected if The installed version falls within these ranges: 10.2.0 through 10.2.7, 11.0.0 through 11.0.4, or 11.1.0 through 11.1.2
-
Verify SSL Forward Proxy statusIn the PAN-OS web interface, go to Network > SSL Forward Proxy, or run 'show ssl-proxy statistics' in the CLI to confirm whether SSL Forward Proxy is enabled.Affected if SSL Forward Proxy is currently enabled (the vulnerability only triggers when this feature is on)
-
Monitor resource utilizationRun 'show system resources' or check the Dashboard for memory usage trends over time. Look for steadily increasing memory consumption.Affected if Memory usage is abnormally high or continuously growing, indicating the leak may be present
A PA-5400 Series device running an affected PAN-OS version (10.2.0-10.2.7, 11.0.0-11.0.4, or 11.1.0-11.1.2) with SSL Forward Proxy enabled is vulnerable to this memory leak issue.
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.411.1.2
If SSL Forward Proxy is not required on PA-5400 Series devices, disable it as a temporary workaround. Otherwise, apply the vendor-supplied PAN-OS patch or upgrade to a fixed version once available.
PAN-OS 10.2.8 (or later 10.2.x), 11.0.5 (or later 11.0.x), or 11.1.3 (or later 11.1.x) depending on your branch; choose nearest fixed version in your current branch
- 1. Identify your current PAN-OS version by navigating to Device > Support in the web interface or using 'show system info' in CLI
- 2. Determine if your device is a PA-5400 Series appliance: check the model number on the device physical label or via 'show system info' output
- 3. Verify if SSL Forward Proxy is enabled: go to Device > SSL Forward Proxy (or Network > SSL Forward Proxy depending on version)
- 4. If you are on a PA-5400 Series with SSL Forward Proxy enabled and affected version, plan for upgrade
- 5. Download the appropriate PAN-OS upgrade from Palo Alto Networks support portal (requires valid support contract)
- 6. Before upgrading, backup your configuration via Device > Setup > Operations > Save named configuration snapshot
- 7. Upload the new PAN-OS image via Device > Software > Upload
- 8. Install the upgrade and reboot the firewall
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3382 — 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-3382 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