{"id":2196,"date":"2016-07-15T10:12:48","date_gmt":"2016-07-15T09:12:48","guid":{"rendered":"http:\/\/emtunc.org\/blog\/?p=2196"},"modified":"2016-07-15T10:12:48","modified_gmt":"2016-07-15T09:12:48","slug":"palo-alto-networks-update-server-api-exposure","status":"publish","type":"post","link":"https:\/\/emtunc.org\/blog\/07\/2016\/palo-alto-networks-update-server-api-exposure\/","title":{"rendered":"Palo Alto Networks &#8211; Update Server API Exposure"},"content":{"rendered":"<p>In this brief post I will relay my finding of a security vulnerability with the Palo Alto update servers. This post refers to the <a href=\"https:\/\/securityadvisories.paloaltonetworks.com\/\" target=\"_blank\">security advisory\u00a0PAN-SA-2016-0010<\/a>.<\/p>\n<p><!--more--><\/p>\n<p>It started with me watching some Palo Alto training videos. I administrate Palo Alto&#8217;s at work so thought it would be good to top-up my\u00a0knowledge on the product and look in to taking the PCNSE. I managed to <em>obtain<\/em> a copy of a Palo Alto VM by following a link in\u00a0the training video.<\/p>\n<p>After setting up and configuring the appliance, I tried to update the PAN-OS release and threat\/application signatures as they were all a bit old but obviously knew that wouldn&#8217;t have worked as you need a license to do pretty much anything with the appliance (technically it would still work as a basic firewall but I wouldn&#8217;t have been able to use\/test\/learn any of the useful features like Global Protect, Wildfire, URL filtering, app-ID, etc).<\/p>\n<p>In the process of trying to get my virtual appliance updated, I discovered a\u00a0number of available functions.<\/p>\n<h3>The Fix<\/h3>\n<ul>\n<li>Most of the APIs that were exposed to the internet had no reason to be, therefore sensitive\/unused\/internal-only APIs have been moved to an internal, non-internet facing server by Palo Alto Networks.<\/li>\n<\/ul>\n<h3>Palo Alto Networks Response and Timeline<\/h3>\n<ul>\n<li>I first reported this issue via the appropriate security disclosure channels\u00a0(SecurityDisclosure@paloaltonetworks.com) on the <strong>6th March 2016<\/strong>.<\/li>\n<li>I received an acknowledgement e-mail from the\u00a0Product Security Incident Response Team\u00a0on the <strong>12th March 2016<\/strong>. The e-mail detailed the process of a security disclosure.<\/li>\n<li>Received a quick update on the <strong>3rd June 2016<\/strong>.<\/li>\n<li>Received another update on the <strong>7th June 2016<\/strong> explaining what PAN are doing to address the issues reported.<\/li>\n<li>Received another update on the <strong>21st June 2016<\/strong>. &#8211; this time with a draft security advisory as well as a more in-depth explanation of what PAN are\/will be doing to address the issues reported.<\/li>\n<\/ul>\n<h3>Closing\u00a0notes<\/h3>\n<p>We live in\u00a0a time where security researchers are\u00a0<a href=\"https:\/\/www.theguardian.com\/technology\/2014\/may\/29\/us-cybercrime-laws-security-researchers\" target=\"_blank\">targeted<\/a>,\u00a0<a href=\"http:\/\/arstechnica.co.uk\/security\/2015\/09\/security-company-sues-to-bar-disclosure-related-to-its-own-flaws\/\" target=\"_blank\">sued<\/a>\u00a0and\u00a0<a href=\"http:\/\/thehackernews.com\/2016\/05\/hack-an-election.html\" target=\"_blank\">jailed<\/a> for reporting and investigating security vulnerabilities; therefore kudos to the incident response team at Palo Alto (specifically Eric Moret who kept in contact the whole time) who were open and transparent from the beginning.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this brief post I will relay my finding of a security vulnerability with the Palo Alto update servers. This post refers to the security advisory\u00a0PAN-SA-2016-0010.<\/p>\n","protected":false},"author":32,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2196","post","type-post","status-publish","format-standard","hentry","category-tech"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p1trTO-zq","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/2196","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/comments?post=2196"}],"version-history":[{"count":2,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/2196\/revisions"}],"predecessor-version":[{"id":2198,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/posts\/2196\/revisions\/2198"}],"wp:attachment":[{"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/media?parent=2196"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/categories?post=2196"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/emtunc.org\/blog\/wp-json\/wp\/v2\/tags?post=2196"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}