CVE-2025-0111High

CVE-2025-0111 PAN-OS: Authenticated File Read Vulnerability in the Management Web Interface

Published
February 12, 2025
Last Modified
March 6, 2025

🔗 CVE IDs covered (1)

📋 Description

An authenticated file read vulnerability in the management web interface of the Palo Alto Networks PAN-OS software enables an authenticated attacker with network access to the management web interface to read files on the PAN-OS filesystem that are readable by the “nobody” user. The attacker must have network access to the management web interface to exploit this issue. You can greatly reduce the risk of this issue by restricting access to the management web interface to only trusted internal IP addresses according to our recommended critical 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 does not affect Cloud NGFW or Prisma Access software.

🎯 Affected products3

  • Cloud NGFW
  • PAN-OS
  • Prisma Access

✅ Remediation

VERSION MINOR VERSION SUGGESTED SOLUTION PAN-OS 10.1 10.1.0 through 10.1.14 Upgrade to 10.1.14-h9 or later PAN-OS 10.2 10.2.0 through 10.2.13 Upgrade to 10.2.13-h3 or later   10.2.7 Upgrade to 10.2.7-h24 or 10.2.13-h3 or later   10.2.8 Upgrade to 10.2.8-h21 or 10.2.13-h3 or later   10.2.9 Upgrade to 10.2.9-h21 or 10.2.13-h3 or later   10.2.10 Upgrade to 10.2.10-h14 or 10.2.13-h3 or later   10.2.11 Upgrade to 10.2.11-h12 or 10.2.13-h3 or later   10.2.12 Upgrade to 10.2.12-h6 or 10.2.13-h3 or later PAN-OS 11.0 (EoL)   Upgrade to a supported fixed version PAN-OS 11.1 11.1.0 through 11.1.6 Upgrade to 11.1.6-h1 or later   11.1.2 Upgrade to 11.1.2-h18 or 11.1.6-h1 or later   11.1.4 Upgrade to 11.1.4-h13 or 11.1.6-h1 or later PAN-OS 11.2 11.2.0 through 11.2.4 Upgrade to 11.2.5 or later   11.2.4 Upgrade to 11.2.4-h4 or 11.2.5 or later All other older   Upgrade to a supported fixed version. unsupported PAN-OS versions Workarounds and mitigations: Recommended mitigation—The vast majority of firewalls already follow Palo Alto Networks and industry best practices. However, if you have not already, we strongly recommend that you secure access to your management interface according to our critical deployment guidelines (https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431). Specifically, you should restrict management interface access to only trusted internal IP addresses. Review information about how to secure management access to your Palo Alto Networks firewalls: * Palo Alto Networks LIVEcommunity article:https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 * Palo Alto Networks official and detailed technical documentation:https://docs.paloaltonetworks.com/best-practices/10-1/administrative-access-best-practices/administrative-access-best-practices/deploy-administrative-access-best-practices Additionally, customers with a Threat Prevention subscription can block attacks for this vulnerability by enabling Threat ID 510000 and 510001 (introduced in Applications and Threats content version 8943). https://docs.paloaltonetworks.com/best-practices/10-1/administrative-access-best-practices/administrative-access-best-practices/deploy-administrative-access-best-practices

🔗 References (1)