CVE-2022-0024
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 vulnerability exists in Palo Alto Networks PAN-OS software that enables an authenticated network-based PAN-OS administrator to upload a specifically created configuration that disrupts system processes and potentially execute arbitrary code with root privileges when the configuration is committed on both hardware and virtual firewalls. This issue does not impact Panorama appliances or Prisma Access customers. This issue impacts: PAN-OS 8.1 versions earlier than PAN-OS 8.1.23; PAN-OS 9.0 versions earlier than PAN-OS 9.0.16; PAN-OS 9.1 versions earlier than PAN-OS 9.1.13; PAN-OS 10.0 versions earlier than PAN-OS 10.0.10; PAN-OS 10.1 versions earlier than PAN-OS 10.1.5.
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 confidenceAn authenticated PAN-OS administrator can upload a specially crafted configuration file that, when committed, disrupts system processes and can lead to arbitrary code execution with root privileges on hardware and virtual firewalls.
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.23>= 9.0.0, < 9.0.16>= 9.1.0, < 9.1.13>= 10.0.0, < 10.0.10>= 10.1.0, < 10.1.5CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 PAN-OS versionRun the command 'show system info' in the PAN-OS CLI or check the Dashboard in the web interface to view the PAN-OS versionAffected 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.13, 10.0.0 to <10.0.10, or 10.1.0 to <10.1.5
-
Verify administrator access existsReview admin account configuration by running 'show admins' in CLI or checking the Administrators section in the web interface under Device > AdministratorsAffected if Any PAN-OS administrator accounts exist on the device, which is required for the authenticated attack vector
-
Inspect recent configuration commitsRun 'show system commit history' in CLI or view the Commit History in the web interface to identify any unexpected or unauthorized configuration commitsAffected if There are commits from accounts you do not recognize or commits performed outside of normal maintenance windows
-
Check for system process disruptionsRun 'show system resources' and 'show system service-queue status' in CLI to look for abnormal process states or failuresAffected if System processes are disrupted, crashed, or showing unexpected states following a recent configuration commit
You are affected if your PAN-OS version is within the vulnerable ranges listed AND an authenticated administrator has the ability to upload and commit configuration files.
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.239.0.169.1.13
Upgrade PAN-OS to the fixed versions (8.1.23, 9.0.16, 9.1.13, 10.0.10, 10.1.5 or later). This is a configuration validation vulnerability during commit that allows privilege escalation to root.
PAN-OS 8.1.23 (or latest 8.1.x), 9.0.16 (or latest 9.0.x), 9.1.13 (or latest 9.1.x), 10.0.10 (or latest 10.0.x), or 10.1.5 (or latest 10.1.x) depending on current branch
- 1. Verify current PAN-OS version by navigating to Device > Support or using 'show system info' command
- 2. Identify the appropriate upgrade path based on current version (8.1.x -> 8.1.23, 9.0.x -> 9.0.16, 9.1.x -> 9.1.13, 10.0.x -> 10.0.10, 10.1.x -> 10.1.5)
- 3. Review Palo Alto Networks Upgrade Guide for pre-upgrade requirements and compatibility checks
- 4. Download the targeted PAN-OS upgrade image from Palo Alto Networks Customer Support Portal
- 5. Create a backup of the current configuration via Device > Setup > Operations > Save named configuration snapshot
- 6. If running in HA (High Availability), review HA upgrade procedures in PAN-OS documentation
- 7. Upload the upgrade 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
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0024 — 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-2022-0024 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