CVE-2024-0011
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 reflected cross-site scripting (XSS) vulnerability in the Captive Portal feature of Palo Alto Networks PAN-OS software enables execution of malicious JavaScript (in the context of an authenticated Captive Portal user’s browser) if a user clicks on a malicious link, allowing phishing attacks that could lead to credential theft.
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 reflected cross-site scripting (XSS) vulnerability exists in the Captive Portal feature of Palo Alto Networks PAN-OS software. The vulnerability allows injection of malicious JavaScript through a crafted URL, which executes in the context of an authenticated Captive Portal user's browser when they click on the malicious link.
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>= 8.1.0, < 8.1.24>= 9.0.0, < 9.0.17>= 9.1.0, < 9.1.13>= 10.0.0, < 10.0.11>= 10.1.0, < 10.1.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 versionRun 'show system info' in the PAN-OS CLI or check the web interface under Device > Summary to obtain the installed PAN-OS version number.Affected if The installed version falls within any of these ranges: 8.1.0 to 8.1.23, 9.0.0 to 9.0.16, 9.1.0 to 9.1.12, 10.0.0 to 10.0.10, or 10.1.0 to 10.1.2.
-
Verify Captive Portal is enabledIn the PAN-OS web interface, go to Network > Captive Portal or run 'show captive-portal status' in the CLI to determine if the Captive Portal feature is configured and active.Affected if Captive Portal is enabled and users authenticate through it.
-
Review URL logs for XSS patternsIn PAN-OS logs, filter Traffic or Threat logs for the Captive Portal redirect URLs and inspect query parameters for suspicious patterns such as '<script>', 'javascript:', or other HTML/JS injection attempts.Affected if Log entries show unexpected script tags or javascript: protocols in Captive Portal URL parameters.
-
Check authentication logs for unusual behaviorExamine Authentication logs or System logs around Captive Portal sessions for unexpected script executions or anomalies that may indicate XSS exploitation.Affected if Authentication or session logs contain evidence of injected script execution or unexpected browser-side behavior.
You are affected if your PAN-OS version is within the affected ranges listed AND Captive Portal is enabled, as the vulnerability requires both conditions to be exploitable.
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 · scoped8.1.249.0.179.1.13
Apply available PAN-OS updates/patches for CVE-2024-0011. As a temporary mitigation, implement URL filtering or WAF rules to detect and block malicious payloads in Captive Portal URLs, and educate users about not clicking untrusted links.
PAN-OS 8.1.24 (or later), 9.0.17 (or later), 9.1.13 (or later), or 10.0.11 (or later) depending on your current branch
- 1. Log in to the PAN-OS web interface or use the CLI with administrative credentials.
- 2. Navigate to Device > Software > Software Updates to check for available updates.
- 3. Download the appropriate fixed version for your current branch: 8.1.24, 9.0.17, 9.1.13, or 10.0.11 (or later).
- 4. Review the PAN-OS Upgrade Guide at paloaltonetworks.com for pre-upgrade checks and procedures.
- 5. Back up the current configuration via Device > Setup > Operations > Save named configuration snapshot.
- 6. Install the software update and reboot the appliance.
- 7. After reboot, verify the system is running the fixed version via the Dashboard or 'show system info' command.
- 8. Test Captive Portal functionality to confirm the fix works correctly.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0011 — 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-0011 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