From 16a57d93e5a5432fc13ac04ecf0e347145fae77d Mon Sep 17 00:00:00 2001 From: CVE Team Date: Sat, 15 Mar 2025 00:00:32 +0000 Subject: [PATCH] "-Synchronized-Data." --- 2025/0xxx/CVE-2025-0115.json | 10 +++++----- 2025/2xxx/CVE-2025-2331.json | 18 ++++++++++++++++++ 2025/2xxx/CVE-2025-2332.json | 18 ++++++++++++++++++ 2025/2xxx/CVE-2025-2333.json | 18 ++++++++++++++++++ 4 files changed, 59 insertions(+), 5 deletions(-) create mode 100644 2025/2xxx/CVE-2025-2331.json create mode 100644 2025/2xxx/CVE-2025-2332.json create mode 100644 2025/2xxx/CVE-2025-2333.json diff --git a/2025/0xxx/CVE-2025-0115.json b/2025/0xxx/CVE-2025-0115.json index 35dfeef74a9..3fc0446aa57 100644 --- a/2025/0xxx/CVE-2025-0115.json +++ b/2025/0xxx/CVE-2025-0115.json @@ -11,7 +11,7 @@ "description_data": [ { "lang": "eng", - "value": "A vulnerability in the Palo Alto Networks PAN-OS software enables an authenticated admin on the PAN-OS CLI to read arbitrary files.\n\nThis issue does not affect Cloud NGFW or Prisma Access." + "value": "A vulnerability in the Palo Alto Networks PAN-OS software enables an authenticated admin on the PAN-OS CLI to read arbitrary files.\n\nThe attacker must have network access to the management interface (web, SSH, console, or telnet) and successfully authenticate to exploit this issue. You can greatly reduce the risk of this issue by restricting access to the management interface to only trusted users and 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 .\n\nThis issue does not affect Cloud NGFW or Prisma Access." } ] }, @@ -182,10 +182,10 @@ { "base64": false, "type": "text/html", - "value": "No special configuration is required to be vulnerable to this issue." + "value": "The risk is greatest if you enabled access to the management interface (HTTP, HTTPS, SSH, or telnet) from the internet or any untrusted network either:
  1. Directly; or
  2. Through a dataplane interface that includes a management interface profile.
You greatly reduce the risk if you ensure that you allow only trusted users and internal IP addresses to access the management interface." } ], - "value": "No special configuration is required to be vulnerable to this issue." + "value": "The risk is greatest if you enabled access to the management interface (HTTP, HTTPS, SSH, or telnet) from the internet or any untrusted network either:\n * Directly; or\n * Through a dataplane interface that includes a management interface profile.\nYou greatly reduce the risk if you ensure that you allow only trusted users and internal IP addresses to access the management interface." } ], "work_around": [ @@ -195,10 +195,10 @@ { "base64": false, "type": "text/html", - "value": "No known mitigations or workarounds exist for this issue." + "value": "Recommended mitigation\u2014The 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. 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:
" } ], - "value": "No known mitigations or workarounds exist for this issue." + "value": "Recommended mitigation\u2014The 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.\n\nReview information about how to secure management access to your Palo Alto Networks firewalls:\n * Palo Alto Networks LIVEcommunity article:\u00a0 https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-ac... https://live.paloaltonetworks.com/t5/community-blogs/tips-amp-tricks-how-to-secure-the-management-access-of-your-palo/ba-p/464431 \n * Palo Alto Networks official and detailed technical documentation: https://docs.paloaltonetworks.com/best-practices/10-1/administrative-access-best-practices/administr... https://docs.paloaltonetworks.com/best-practices/10-1/administrative-access-best-practices/administrative-access-best-practices/deploy-administrative-access-best-practices" } ], "exploit": [ diff --git a/2025/2xxx/CVE-2025-2331.json b/2025/2xxx/CVE-2025-2331.json new file mode 100644 index 00000000000..5a9bace793b --- /dev/null +++ b/2025/2xxx/CVE-2025-2331.json @@ -0,0 +1,18 @@ +{ + "data_type": "CVE", + "data_format": "MITRE", + "data_version": "4.0", + "CVE_data_meta": { + "ID": "CVE-2025-2331", + "ASSIGNER": "cve@mitre.org", + "STATE": "RESERVED" + }, + "description": { + "description_data": [ + { + "lang": "eng", + "value": "** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided." + } + ] + } +} \ No newline at end of file diff --git a/2025/2xxx/CVE-2025-2332.json b/2025/2xxx/CVE-2025-2332.json new file mode 100644 index 00000000000..a0b895c1829 --- /dev/null +++ b/2025/2xxx/CVE-2025-2332.json @@ -0,0 +1,18 @@ +{ + "data_type": "CVE", + "data_format": "MITRE", + "data_version": "4.0", + "CVE_data_meta": { + "ID": "CVE-2025-2332", + "ASSIGNER": "cve@mitre.org", + "STATE": "RESERVED" + }, + "description": { + "description_data": [ + { + "lang": "eng", + "value": "** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided." + } + ] + } +} \ No newline at end of file diff --git a/2025/2xxx/CVE-2025-2333.json b/2025/2xxx/CVE-2025-2333.json new file mode 100644 index 00000000000..b1d2bdcbf8d --- /dev/null +++ b/2025/2xxx/CVE-2025-2333.json @@ -0,0 +1,18 @@ +{ + "data_type": "CVE", + "data_format": "MITRE", + "data_version": "4.0", + "CVE_data_meta": { + "ID": "CVE-2025-2333", + "ASSIGNER": "cve@mitre.org", + "STATE": "RESERVED" + }, + "description": { + "description_data": [ + { + "lang": "eng", + "value": "** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided." + } + ] + } +} \ No newline at end of file