Synopsis
While developing a plugin to detect PAN-SA-2016-0005, Tenable discovered a different vulnerability in the panUserLogin() function within panmodule.so that could result in an unauthenticated remote DoS. The PAN-OS function calls the glibc strcpy_chk() function to copy a user-supplied username and password to a buffer. If the 'username' parameter exceeds 0x100 bytes or the 'password' parameter exceeds 0x80 bytes, strcpy_chk() causes the process to terminate. When the process terminates, it is re-spawned by its parent process, so it may not be obvious that process had died and may be a partial DoS scenario like previous. However, the log will show it had:
2016-03-19 01:21:34.256 -0400 INFO: appweb: exited, Core: True, Exit signal: SIGABRT
2016-03-19 01:21:48.875 -0400 INFO: appweb: process running with pid 6700
This has been tested on PAN-OS 7.0.1 running on a VM-series firewall.
Solution
Palo Alto has released version 7.0.8 and 7.1.0 to address this issue.
Additional References
https://www.paloaltonetworks.com/documentation/70/pan-os/pan-os-release-notes/pan-os-7-0-8-addressed-issues#78342http://securityadvisories.paloaltonetworks.com/Home/Detail/41
Disclosure Timeline
All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.
Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.
For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.
If you have questions or corrections about this advisory, please email [email protected]