dbcve.org
Pan OsOperating system · Paloaltonetworks

CVE-2024-5913

MEDIUM · 6.8 CVSS v3.1 Published 2024-07-10
Fix available
A fix is available. Upgrade to 10.1.14 / 10.2.10 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
An improper input validation vulnerability in Palo Alto Networks PAN-OS software enables an attacker with the ability to tamper with the physical file system to elevate privileges.

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 · moderate confidence

An improper input validation vulnerability in Palo Alto Networks PAN-OS software allows an attacker with the capability to tamper with the physical file system to elevate privileges to a higher level than intended.

MitigationApply the vendor-supplied patch for PAN-OS when available; restrict physical access to infrastructure and monitor for unauthorized file system modifications as a compensating control.

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
Pan OsOperating system
Affected:>= 10.1.0, < 10.1.14>= 10.2.0, < 10.2.10>= 11.0.0, < 11.0.5>= 11.1.0, < 11.1.4>= 11.2.0, < 11.2.1= 10.1.14

CVSS 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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify PAN-OS software version
    Run the command 'show system info' or check the Dashboard in the PAN-OS web interface to retrieve the installed PAN-OS version number
    Affected if The installed version falls within any of these ranges: 10.1.0 through 10.1.14 (exclusive of 10.1.14 unless explicitly marked as affected), 10.2.0 through 10.2.10, 11.0.0 through 11.0.5, 11.1.0 through 11.1.4, or 11.2.0 through 11.2.1; or equals exactly 10.1.14 per the explicit notation. If the vers
  2. Confirm physical access exposure
    Determine whether the physical security controls on network infrastructure are adequate: verify that PAN-OS hardware appliances are located in restricted-access facilities, locked racks, or secured rooms with access logging
    Affected if The system is affected ONLY if both conditions are true: (1) the PAN-OS version matches an affected version range as identified in step 1, AND (2) unauthorized physical access to the appliance file system is theoretically possible by an attacker

A system is affected by CVE-2024-5913 only if it runs a PAN-OS version within the affected ranges AND an attacker could gain physical access to tamper with the file system, since the vulnerability requires physical tampering to elevate privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.1.14 / 10.2.10 / 11.0.5 or later
Fixed in 10.1.1410.2.1011.0.5
Interim mitigation

Apply the vendor-supplied patch for PAN-OS when available; restrict physical access to infrastructure and monitor for unauthorized file system modifications as a compensating control.

Recommended fix Moderate confidence

Upgrade to the appropriate fixed version: 10.1.14, 10.2.10, 11.0.5, or 11.1.4 based on your current branch

  1. 1. Identify the current PAN-OS version by navigating to Device > Support or using 'show system info' in the CLI
  2. 2. Determine which version branch the current installation belongs to (10.1.x, 10.2.x, 11.0.x, or 11.1.x)
  3. 3. For PAN-OS 10.1.x: Upgrade to version 10.1.14 or later
  4. 4. For PAN-OS 10.2.x: Upgrade to version 10.2.10 or later
  5. 5. For PAN-OS 11.0.x: Upgrade to version 11.0.5 or later
  6. 6. For PAN-OS 11.1.x: Upgrade to version 11.1.4 or later
  7. 7. After upgrade, verify the new version is running using 'show system info'
  8. 8. Test that critical functionality and administrative access work as expected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pan Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5913 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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