admin/cvelist
1
0
Fork 0
mirror of https://github.com/CVEProject/cvelist.git synced 2025-05-09 03:57:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update CVE-2020-2035 to include PAN-OS 10.1

Browse Source
This commit is contained in:
Chandan 2021-06-09 09:50:25 -07:00
parent ad747940e1
commit 0f8dbb02ba
No known key found for this signature in database
GPG Key ID: 76A1F9BB8C9E02F5
1 changed files with 21 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
2020/2xxx/CVE-2020-2035.json
View File

@ -35,6 +35,11 @@
"version_affected": "=",
"version_name": "10.0",
"version_value": "10.0.*"
},
{
"version_affected": "=",
"version_name": "10.1",
"version_value": "10.1.*"
}
]
}
@ -65,7 +70,7 @@
"description_data": [
{
"lang": "eng",
"value": "When SSL/TLS Forward Proxy Decryption mode has been configured to decrypt the web transactions, the PAN-OS URL filtering feature inspects the HTTP Host and URL path headers for policy enforcement on the decrypted HTTPS web transactions but does not consider Server Name Indication (SNI) field within the TLS Client Hello handshake. This allows a compromised host in a protected network to evade any security policy that uses URL filtering on a firewall configured with SSL Decryption in the Forward Proxy mode. A malicious actor can then use this technique to evade detection of communication on the TLS handshake phase between a compromised host and a remote malicious server. This technique does not increase the risk of a host being compromised in the network. It does not impact the confidentiality or availability of a firewall. This is considered to have a low impact on the integrity of the firewall because the firewall fails to enforce a policy on certain traffic that should have been blocked. This issue does not impact the URL filtering policy enforcement on clear text or encrypted web transactions. This technique can be used only after a malicious actor has compromised a host in the protected network and the TLS/SSL Decryption feature is enabled for the traffic that the attacker controls. Palo Alto Networks is not aware of any malware that uses this technique to exfiltrate data. This issue is applicable to all current versions of PAN-OS."
"value": "When SSL/TLS Forward Proxy Decryption mode has been configured to decrypt the web transactions, the PAN-OS URL filtering feature inspects the HTTP Host and URL path headers for policy enforcement on the decrypted HTTPS web transactions but does not consider Server Name Indication (SNI) field within the TLS Client Hello handshake.\n\nThis allows a compromised host in a protected network to evade any security policy that uses URL filtering on a firewall configured with SSL Decryption in the Forward Proxy mode. A malicious actor can then use this technique to evade detection of communication on the TLS handshake phase between a compromised host and a remote malicious server.\n\nThis technique does not increase the risk of a host being compromised in the network. It does not impact the confidentiality or availability of a firewall. This is considered to have a low impact on the integrity of the firewall because the firewall fails to enforce a policy on certain traffic that should have been blocked.\n\nThis issue does not impact the URL filtering policy enforcement on clear text or encrypted web transactions.\n\nThis technique can be used only after a malicious actor has compromised a host in the protected network and the TLS/SSL Decryption feature is enabled for the traffic that the attacker controls.\n\nPalo Alto Networks is not aware of any malware that uses this technique to exfiltrate data.\n\nThis issue is applicable to all current versions of PAN-OS. This issue does not impact Panorama or WF-500 appliances."
}
]
},
@ -109,14 +114,12 @@
"references": {
"reference_data": [
{
"refsource": "MISC",
"url": "https://security.paloaltonetworks.com/CVE-2020-2035",
"name": "https://security.paloaltonetworks.com/CVE-2020-2035"
"refsource": "CONFIRM",
"url": "https://security.paloaltonetworks.com/CVE-2020-2035"
},
{
"refsource": "MISC",
"url": "https://www.mnemonic.no/blog/introducing-snicat/",
"name": "https://www.mnemonic.no/blog/introducing-snicat/"
"refsource": "CONFIRM",
"url": "https://www.mnemonic.no/blog/introducing-snicat/"
}
]
},
@ -137,12 +140,22 @@
"lang": "eng",
"time": "2020-08-12T16:00:00.000Z",
"value": "Initial publication"
},
{
"lang": "eng",
"time": "2021-03-03T17:00:00.000Z",
"value": "Added clarification that Panorama and WF-500 appliances are not impacted"
},
{
"lang": "eng",
"time": "2021-06-09T16:00:00.000Z",
"value": "Updated impacted versions to include PAN-OS 10.1"
}
],
"work_around": [
{
"lang": "eng",
"value": "Customers concerned about the risk described in this advisory are encouraged to review the KB article https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u0000008V4J for more information on background and mitigation options. To enforce URL filtering policy on TLS handshakes for decrypted HTTPS sessions, we suggest you use any one of the following workarounds:\n\n1. Route outbound traffic between two virtual systems (vsys) on PAN-OS firewalls that have vsys capability and perform URL Filtering on one vsys and perform SSL/TLS Decryption on the other vsys.\n\n2. Add two additional Security Zones and route outbound traffic between the two zones so that you can apply both \"Decrypt\" and \"No Decrypt\" Decryption policy rules. For example, configure your next-generation firewall so that traffic travels from the Inside zone to the Internal-DMZ zone where you applied a \u201cNo Decrypt\u201d rule along with URL Filtering and then the traffic passes to the External-DMZ zone and from External-DMZ to the Internet zone where you applied a \"Decrypt\" rule. Be aware that this workaround configuration may significantly increase the load on your firewall.\n\n3. Use the additional security device in the traffic chain. \nThe SSL/TLS Decryption and URL Filtering functions should be separated (for example, the first device is performing URL Filtering and the second device is performing SSL/TLS Decryption).\n\nThese workarounds are described in detail at https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u0000008V4J\n\nWe recommend you use an endpoint protection solution such as the Cortex XDR agent to significantly reduce the potential risk of hosts being compromised. See https://www.paloaltonetworks.com/cortex/endpoint-protection.\n\nCaution: We recommend that you do not disable SSL/TLS Decryption as a workaround to this issue. There are additional risks associated with this action. \n"
"value": "Customers concerned about the risk described in this advisory are encouraged to review the KB article https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u0000008V4J for more information on background and mitigation options. To enforce URL filtering policy on TLS handshakes for decrypted HTTPS sessions, we suggest you use any one of the following workarounds:\n\n1. Route outbound traffic between two virtual systems (vsys) on PAN-OS firewalls that have vsys capability and perform URL Filtering on one vsys and perform SSL/TLS Decryption on the other vsys.\n\n2. Add two additional Security Zones and route outbound traffic between the two zones so that you can apply both \"Decrypt\" and \"No Decrypt\" Decryption policy rules. For example, configure your next-generation firewall so that traffic travels from the Inside zone to the Internal-DMZ zone where you applied a “No Decrypt” rule along with URL Filtering and then the traffic passes to the External-DMZ zone and from External-DMZ to the Internet zone where you applied a \"Decrypt\" rule. Be aware that this workaround configuration may significantly increase the load on your firewall.\n\n3. Use the additional security device in the traffic chain. \nThe SSL/TLS Decryption and URL Filtering functions should be separated (for example, the first device is performing URL Filtering and the second device is performing SSL/TLS Decryption).\n\nThese workarounds are described in detail at https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u0000008V4J\n\nWe recommend you use an endpoint protection solution such as the Cortex XDR agent to significantly reduce the potential risk of hosts being compromised. See https://www.paloaltonetworks.com/cortex/endpoint-protection.\n\nCaution: We recommend that you do not disable SSL/TLS Decryption as a workaround to this issue. There are additional risks associated with this action. \n"
}
]
}