CVE-2017-15944Palo Alto Networks PAN-OS Remote Code Execution Vulnerability
CVE-2017-15944 is a improper input validation in Palo Alto Networks PAN-OS, rated critical (9.8 on CVSS 3.1).
Why this priority: Exploited in the wild: listed in CISA's KEV catalog.
Published · Updated · NVD status: Analyzed
What it is
The software trusts input it should check, so crafted values reach code that assumes they are well formed. Code reads or writes outside the memory it was given, which can corrupt the process.
How it is reached
An attacker can exploit it over the network, without an account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker drive the component into behaviour its authors did not intend.
Is it being exploited?
CISA added it to the Known Exploited Vulnerabilities catalog on 2022-08-18: it is being exploited in the wild. It can be exploited automatically, at scale. EPSS estimates a 98% chance of exploitation activity in the next 30 days, higher than 100% of scored CVEs.
What to do
- Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2022-09-08.
- Upgrade Palo Alto Networks PAN-OS to a fixed version for your release line (6.1.19, 7.0.19, 7.1.14).
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
- Check exposed instances for signs of compromise, not only for the version.
Description from NVD
Palo Alto Networks PAN-OS before 6.1.19, 7.0.x before 7.0.19, 7.1.x before 7.1.14, and 8.0.x before 8.0.6 allows remote attackers to execute arbitrary code via vectors involving the management interface.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Network edge devices: VPNs, firewalls, routers and gateways. They sit between the internet and internal networks, so a flaw in one is often the first step into everything behind it.
- Operating systems on servers, workstations or devices. Everything on the host inherits the flaw.
- Interfaces that accept external input. The flaw sits at the input boundary of the affected component.
- Native code: operating systems, browsers and firmware. The flaw sits wherever native code reads untrusted data.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- At the input boundary of the affected component. An attacker who crosses it can drive the component into behaviour its authors did not intend.
- Wherever native code reads untrusted data. An attacker who crosses it can crash the process, read memory, or in the worst case run code.
Questions to answer about your own systems
- Where does Palo Alto Networks PAN-OS run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.