deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

Check Point patches world-writable Gaia socket that let any local process run root commands

Check Point has fixed a Gaia OS flaw where a root-level daemon executed commands from any local process through a world-writable Unix socket, with active exploitation already recorded.

Check Point patches world-writable Gaia socket that let any local process run root commands

A root daemon with no authentication

Check Point has shipped fixes for a local privilege escalation in Gaia OS, the operating system that powers its security appliances, after recording active exploitation against roughly two dozen customers in a single region. Tracked as CVE-2026-123039 with a CVSS score of 7.8, the flaw sits in a daemon called dynamic_server that runs as root and serves Gaia's extended command-line interface behind the documented Clish shell.

According to a Netics Labs write-up on dev.to, which draws on Check Point's advisory, the daemon listens on a Unix domain socket at /tmp/dynamic_socket. On affected builds that socket is created with mode 0777, meaning any account on the appliance can connect, and the daemon does not authenticate the connecting process before executing the command it receives. The result is that any local user able to run code on the appliance can turn that foothold into root with a single request.

The precondition matters: this is not a standalone remote entry point. An attacker needs local code execution first, and the bug converts limited access into full control.

Affected products and where the fix landed

The advisory lists Check Point Force Firewalls, Management and Log Servers, Multi-Domain Security Management and Multi-Domain Log Server, and Maestro Orchestrator as affected, across R81, R81.10, R81.20, R82, R82.10 and R82.20. Spark Firewalls and Smart-1 Cloud sit outside the exposure.

The fix ships in four jumbo hotfix accumulators: R82.20 from Take 14, R82.10 from Take 52, R82 from Take 132, and R81.20 from Take 174. Per the Netics write-up, NVD describes the vulnerable side of those same branches as Take 10 or below, 50 or below, 130 or below and 173 or below. Where a maintenance window is not immediate, Check Point's workaround is to disable the dynamic_server process and stop it from restarting, at the stated cost of Dynamic CLI commands no longer working.

How the flaw was used

Check Point Research documented an intrusion chain in which the socket was the second step. Initial access came through PHP2Shell in the Mobile Access portal, tracked as CVE-2026-109618 and CVE-2026-109619 at 9.2, which gave code execution in the portal. The unauthenticated socket then elevated that to root.

With root, the operators wrote PHP webshells into the portal's template directory, including one in a file named zz.tpl that gates access behind a hardcoded key and supports operating-system commands, PHP evaluation and file uploads. A standalone backdoor called TSGA was dropped as /tmp/CPconfigdaemon and relaunched from the boot persistence directory as slot_CPconfigdaemon, alongside an embedded shared library named TSProxy written to /lib/libcpfwcommon.so so that selected appliance processes carry the attacker's traffic. From there the actors ran the gogo scanner to map the internal network, moved over SSH to a VMware ESXi host using the vpxuser service account, and executed a wiper named destroy_v6.

The activity ran from 30 October to 4 November 2026 in two waves: a first on 30 October against Israeli organisations, some of which suffered destructive action, and a broader second on 2 November spanning several countries and sectors with no destructive activity observed. Requests clustered between 00:00 and 09:00 UTC, peaking in the first two hours, a pattern the researchers link to working hours in one region and a useful signal for anyone reviewing portal logs at odd hours.

Verifying the patch

Two checks confirm the fix landed, according to the advisory. The socket should now appear as srw-rw---- root config, mode 0660; a build still showing srwxrwxrwx remains in the vulnerable world-writable state. The daemon log should also record rejected connections from unauthorised users, visible by grepping /var/log/dynamicCli.log for entries such as a rejection tied to uid 99. A burst of those rejections correlating with portal authentication events is worth investigating.

Why it matters

A firewall or management server holds the policy, the credentials and the trust relationships of the network it protects, so root on the appliance is not containment, it is position. The documented campaign shows that trajectory end to end: from a portal bug, to root via an unauthenticated socket, to a hypervisor and a wiper. Patching is only half the work; verifying the socket mode and scanning the daemon log on every box closes the loop, and internet-facing appliances should go first.

  • #security
  • #check-point
  • #vulnerability
  • #privilege-escalation
  • #gaia-os
  • #patching

Related posts