CVE-2024-0012
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 · uneditedAn authentication bypass in Palo Alto Networks PAN-OS software enables an unauthenticated attacker with network access to the management web interface to gain PAN-OS administrator privileges to perform administrative actions, tamper with the configuration, or exploit other authenticated privilege escalation vulnerabilities like CVE-2024-9474 https://security.paloaltonetworks.com/CVE-2024-9474 . The risk of this issue is greatly reduced if you secure access to the management web interface by restricting access to only trusted internal IP addresses according to our recommended best practice deployment guidelines https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 . This issue is applicable only to PAN-OS 10.2, PAN-OS 11.0, PAN-OS 11.1, and PAN-OS 11.2 software. Cloud NGFW and Prisma Access are not impacted by this vulnerability.
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 confidenceAuthentication bypass in PAN-OS management web interface allows unauthenticated attackers with network access to gain full administrator privileges, enabling configuration tampering and chaining with other vulnerabilities like CVE-2024-9474. The vulnerability affects PAN-OS versions 10.2, 11.0, 11.1, and 11.2.
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.1= 10.2.2= 10.2.3= 10.2.4= 10.2.5= 10.2.6= 10.2.7= 10.2.8= 10.2.9= 10.2.10= 10.2.11CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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' in the PAN-OS CLI or check the Dashboard in the web interface to locate the PAN-OS version fieldAffected if The version shown matches 10.2.0 through 10.2.11 (any of the listed affected versions)
-
Confirm management web interface is enabledIn the PAN-OS web interface, go to Device > Setup > Management and verify the Management Web Server setting is enabledAffected if The management web interface is enabled and running
-
Determine management interface network exposureIn the PAN-OS web interface, go to Network > Interfaces and review which interfaces have the management service enabled. Check Device > Setup > Management > General Settings for permitted IP addresses for the management web interfaceAffected if The management web interface is bound to any interface other than a dedicated management-only interface, or is accessible from non-trusted IP ranges
-
Audit admin account configurationRun 'show admins' in the PAN-OS CLI or go to Device > Administrators in the web interface to review administrator accounts for unexpected additions or changesAffected if New or unrecognized administrator accounts exist that were not created by authorized personnel
The environment is affected if PAN-OS version 10.2.0 through 10.2.11 is running AND the management web interface is network-accessible from untrusted or external IP addresses.
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 · scopedRestrict access to the PAN-OS management web interface to trusted internal IP addresses only, and apply vendor-supplied patches or upgrades to fixed PAN-OS versions.
Latest maintenance release in your PAN-OS version branch (10.2.x, 11.0.x, 11.1.x, or 11.2.x) - contact Palo Alto Networks support for specific fixed version details
- Identify your current PAN-OS version by navigating to Device > Support in the web interface or using 'show system info' in the CLI
- Download and install the latest PAN-OS maintenance release for your version branch (10.2.x, 11.0.x, 11.1.x, or 11.2.x) that includes the fix for CVE-2024-0012
- After upgrade, verify the fix by confirming the management interface requires proper authentication
- Alternatively, as a compensating control: Navigate to Network > Network Profiles > Interface Management and restrict the Management profile to trusted internal IP addresses only, or configure a dedicated Management interface with access restricted to your internal management subnets
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0012 — 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-0012 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