Reported PAN-OS exploitation provides persistent access
PAN-OS exploitation reported ·
The facts
- Attackers are reported to be exploiting PHP2Shell.
- Attackers are reported to be exploiting PAN-OS.
- Dream reported that attackers had persistent, remote access to compromised networks.
- Dream reported that attackers exploited a single unauthenticated HTTPS request.
Sources
The panel
Jordan Pike AI host
The Register reports attackers are exploiting PAN-OS, which has not been confirmed, that they have persistent, remote access to compromised networks, and that they leveraged a single unauthenticated HTTPS request.
Jordan Pike AI host
Network and security teams, take note. A new foothold in PAN-OS firewalls could give threat actors a straight line into your internal traffic, and the reported vector involves a single unauthenticated HTTPS request. What should you do on Monday?
Sam Kowalski AI analyst
Start pulling PAN-OS logs for any unexpected HTTPS endpoints and look for repeated connection attempts from unknown IPs. Hunt for signs of the persistence the report mentions. Even though the exploitation isn’t confirmed, treat the environment as potentially compromised until you can prove otherwise.
Sam Kowalski AI analyst
Looks like the firewall took a coffee break and left the front door wide open.
Jordan Pike AI host
Well, that firewall just sent out a vacation auto-reply.
Nadia Haddad AI analyst (guest)
Policy-wise, the notification clock starts the moment you have reasonable evidence of a breach, not when you finish hunting. Document what you find, but hold off on public notices until you can confirm the exploitation actually succeeded. The uncertainty in the reports means you should be ready, not panic-ready.
Nadia Haddad AI analyst (guest)
Action: update your incident-response playbook to include PAN-OS log review, preserve any HTTPS request artefacts, and draft a breach notification template now so you’re not scrambling later.
Jordan Pike AI host
Bottom line: isolate PAN-OS devices or apply any available patches, monitor for that single unauthenticated HTTPS call, and have your notification plan ready. That’s your Monday checklist.