CVE-2023-6792
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 OS command injection vulnerability in the XML API of Palo Alto Networks PAN-OS software enables an authenticated API user to disrupt system processes and potentially execute arbitrary code with limited privileges on the firewall.
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 confidenceOS command injection vulnerability in the XML API of Palo Alto Networks PAN-OS allows an authenticated API user with limited privileges to potentially execute arbitrary code on the firewall by injecting OS commands through the API interface.
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.15>= 10.0.0, < 10.0.12>= 10.1.0, < 10.1.6CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 'show system info' via CLI or check the web interface under Device > Setup > Operations > Device Information. Look for the 'PAN-OS' or 'Software Version' field.Affected if The installed version falls within any of these ranges: 8.1.0 to 8.1.24, 9.0.0 to 9.0.17, 9.1.0 to 9.1.15, 10.0.0 to 10.0.12, or 10.1.0 to 10.1.6.
-
Confirm XML API is accessibleVerify the firewall has the XML API endpoint enabled. Check under Device > Setup > Management > API Settings, or attempt to reach https://<firewall-ip>/api/ from an authorized host. Look for the 'Enable XML API' setting.Affected if The XML API is enabled and reachable on the device.
-
Review API user accountsList all API users under Device > Access Control > API Keys, or run 'show admins' in CLI. Identify any users with API key access, particularly those with 'read-only' or limited role assignments.Affected if Any API user account exists with authentication capabilities, even with limited privileges.
-
Check XML API exposureReview the management interface settings under Network > Interfaces > Management. Determine if the XML API is bound to an interface accessible from untrusted networks (such as outside-facing interfaces or DMZ).Affected if The XML API is accessible from interfaces other than dedicated management networks, or from the internet.
-
Audit API access logsRun 'show log system' filtering for 'api' or 'xml-api' events, or check the Traffic logs for API activity. Look for API requests originating from unexpected sources.Affected if API access occurs from IP addresses outside of trusted administrative subnets.
You are affected if the PAN-OS version is within any of the listed vulnerable ranges AND the XML API is enabled and accessible, regardless of API user privilege level.
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.15
Apply the vendor-supplied patch for PAN-OS per Palo Alto Networks security advisory; restrict XML API access to trusted IP addresses and minimize privileges for API users until patched.
Upgrade to PAN-OS 8.1.24 (or latest 8.1.x), 9.0.17 (or latest 9.0.x), 9.1.15 (or latest 9.1.x), or 10.0.12 (or latest 10.0.x) based on your current branch
- Identify your current PAN-OS version from the Device > Dashboard or via 'show system info' command
- Determine which version branch you are on (8.1.x, 9.0.x, 9.1.x, or 10.0.x)
- Download the appropriate fixed release from the Palo Alto Networks Support Portal: 8.1.24 for 8.1.x, 9.0.17 for 9.0.x, 9.1.15 for 9.1.x, or 10.0.12 for 10.0.x
- Review the PAN-OS Upgrade Guide and release notes for your target version for any pre-upgrade requirements
- Back up your PAN-OS configuration via Device > Setup > Operations > Save config or 'save config' command
- Upload the new PAN-OS image via Device > Software or via CLI: 'request system software upload <filename>'
- Install the software: Device > Software > Install or via CLI: 'request system software install <filename>'
- Reboot the firewall after installation completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6792 — 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-2023-6792 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