Unauthenticated Java Debug Interface in Perforce P4 Search

Executive Summary

This vulnerability affects Perforce P4 Search container images before version 2026.4.2. It exposes an unauthenticated Java debug interface that allows remote attackers to execute arbitrary code as the P4 Search service account. This could lead to full compromise of the connected P4 Server if exploited.

Useful 0 Not Useful 0

Detection Guidance

Check if the Perforce P4 Search container is running with exposed Java debug ports (typically 8000). Use commands like 'netstat -tulnp | grep 8000' or 'ss -tulnp | grep 8000' to identify listening debug interfaces. Verify container configurations for enabled Java debug options such as '-agentlib:jdwp'.

Useful 0 Not Useful 0

Impact Analysis

If you use Perforce P4 Search container images prior to 2026.4.2, an attacker with network access to the Java debug interface could gain control of your P4 Search service. This may allow them to access or modify sensitive data, disrupt operations, or pivot to other systems connected to the P4 Server.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could lead to unauthorized access or data breaches, which may violate compliance requirements under GDPR, HIPAA, or other regulations. Organizations using affected versions may face legal penalties, reputational damage, and mandatory breach notifications depending on the data exposed.

Useful 0 Not Useful 0

Mitigation Strategies

Upgrade Perforce P4 Search to version 2026.4.2 or later to patch the vulnerability. If immediate upgrade is not possible, disable the Java debug interface by removing '-agentlib:jdwp' from container startup arguments and restrict network access to the debug port using firewall rules.

Useful 0 Not Useful 0