BlackTree Security · Infrastructure · Automation · AI

A Trusted Agent Can Run Code on an Unpatched OpenVox Server

A certificate that lets an OpenVox agent submit a report can also become a route into the server that manages the fleet. A critical deserialisation flaw allows a crafted event in that report to execute code on the server. The immediate priority is the central management infrastructure, including primary servers and compilers, rather than treating every endpoint with an agent package as equally exposed.

The OpenVox advisory published on 3 November, GHSA-ffr6-rwpm-p5wq, rates the issue at 9.4 under CVSS 4.0. An attacker normally needs a valid OpenVox or Puppet client certificate and network access to the report service. Permissive certificate autosigning can make that credential obtainable by an otherwise unauthorised caller.

The report crosses a server-side execution boundary

Agents report the results of configuration enforcement to the server. A report records changes, failures and events, which makes it an expected part of normal operations. The vulnerable path is the PUT /puppet/v3/report interface: event data can request reconstruction of a rich Ruby value instead of remaining ordinary report data.

The advisory demonstrates code execution as the puppet service user. This is not a claim of automatic root access. It is still a serious boundary failure because the recipient is a central management service, with whatever configuration, credentials and infrastructure access that deployment grants it.

The advisory also warns about access to the certificate authority’s signing key and possible onward command execution where particular orchestration arrangements are configured. The key exposure depends on the server having access to it; a compiler without the CA role does not automatically hold that key. Assess the server’s real permissions and trust relationships, without assuming that every managed host has already been compromised.

Update the agent code on the server, not just the endpoints

The package names can obscure where the fix must be applied. The OpenVox release notes explain that OpenVox Server executes the agent’s Ruby code when processing reports. The corrected converter keeps event values as data. An agent package installed on a server therefore matters differently from the same package on an endpoint that only sends reports.

The project’s coordinated security announcement identifies these first fixed OpenVox package versions:

Package 8.x branch 9.x branch
openvox-agent 8.32.0 9.3.0
openvox-server 8.18.0 9.2.0

The OpenVox Server 9.2.0 notes say its package requires agent 9.3.0 or later and restarts the service during installation. If only the agent package is upgraded on a server, the project instructs operators to restart puppetserver themselves. Replacing files on disk does not establish that the running service has loaded the corrected implementation.

There is also a scope detail worth preserving. The GitHub advisory’s affected-version fields stop at agent 9.2.0 and server 9.1.0, while the release histories include later 9.2.1 and 9.1.1 builds before the fixes above. An omitted version is not a reliable all-clear. Match the complete installed package pair to the project’s security release guidance, or obtain confirmation for a downstream backport.

Agent-only hosts are not exposed through this server report-processing path, according to the release notes, and can follow their normal upgrade schedule. Prioritise the hosts that receive and process reports. Check every primary, compiler and relevant recovery image so failover or rebuilding does not quietly restore the vulnerable combination.

The related Puppet Enterprise issue is now in CISA’s exploited catalogue

OpenVox’s GitHub advisory still displays no assigned CVE in its dedicated identifier field. It explicitly relates the flaw to the Puppet Enterprise report-deserialisation issue, CVE-2026-115731. Keep those product identities and their package versions distinct.

CISA announced on 17 November that it had added the Perforce Puppet Enterprise vulnerability to its Known Exploited Vulnerabilities catalogue based on evidence of active exploitation. That is a concrete escalation for the related issue. The bulletin does not identify an OpenVox victim, a particular campaign or proof that an individual OpenVox deployment has been attacked.

Reduce the certificate exposure and verify the change

For systems that cannot immediately upgrade, Vox Pupuli recommends limiting server access to networks that need it and disabling or tightening autosigning. These measures reduce the set of callers able to reach the vulnerable path. They do not repair report deserialisation, and should remain tracked as temporary controls with an owner and a supported update plan.

Review certificate issuance as well as the currently enrolled nodes. Establish whether untrusted callers could obtain a signed identity, whether unexpected certificates were approved, and which report-processing hosts those identities could reach. Preserve relevant enrolment, application and endpoint evidence before making changes that could erase it. Investigate unusual service processes or changes under the server account through the incident-response process.

After updating, record both installed package versions, the service restart and a successful legitimate agent report. Test necessary authentication and configuration-enforcement flows. The coordinated server release also changes certificate-name authorisation, so the project specifically asks operators to validate custom auth.conf rules after upgrading. That related fix is another reason to test the complete deployment rather than copying one package number into a closure ticket.

If investigation indicates that a server or signing key was accessed, a version update alone cannot restore trust. Assess certificates, credentials and managed-system relationships as part of recovery. For routine closure, the useful evidence is a corrected, restarted report-processing service with its expected clients and permissions verified.

Leave a Reply

Your email address will not be published. Required fields are marked *