Summary
PowerJob versions 4.x through 5.1.2 contain a critical authentication weakness in the /friend/process endpoint of the Server-Worker transport layer. Because the endpoint can be reached without authentication, an unauthenticated attacker may be able to trigger remote code execution on an exposed PowerJob service.
Affected context
The vulnerability occurs in PowerJob deployments using the affected Server-Worker transport layer and exposing the /friend/process endpoint. Risk is greatest when the service is reachable by untrusted networks and the endpoint processes attacker-controlled requests without first establishing a valid authenticated identity.
Exploit preconditions
- Attack surface: Network-accessible PowerJob Server-Worker transport endpoint
- Required access: No valid credentials are required when the vulnerable endpoint is exposed
- Trigger point: A request to
/friend/process - Why exploitation is possible: The endpoint permits processing before enforcing effective authentication, allowing unauthenticated input to reach code paths capable of executing operations on the server
Why this happens
The underlying bug is an authorization boundary failure caused by missing or ineffective authentication enforcement on a sensitive transport-layer endpoint. This maps to CWE-287: Improper Authentication, where the application does not reliably verify the identity of a requester before allowing access to protected functionality. When such functionality processes attacker-controlled requests with server-side execution effects, the authentication flaw can result in remote code execution.
Potential impact
- An unauthenticated attacker may execute arbitrary code in the PowerJob server context
- The attacker could access, alter, or destroy data available to the service
- Compromised credentials or configuration secrets could be exposed
- The affected host may be used for lateral movement or disruption of worker workloads
- Job definitions, processing workflows, or related operational data may be manipulated
General mitigation guidance
Mitigation typically focuses on enforcing authentication and authorization before any sensitive endpoint processing occurs.
Common defensive patterns include:
- Require strong, explicit authentication for all Server-Worker transport endpoints
- Apply endpoint-level authorization and reject requests lacking the required role or service identity
- Restrict transport interfaces to trusted networks through segmentation and access controls
- Use mutually authenticated service-to-service communication where appropriate
- Run PowerJob components with least privilege and isolate execution workloads
- Disable or remove unused transport endpoints and avoid exposing administrative interfaces publicly
- Treat all unauthenticated requests as untrusted and validate them before processing
How teams detect issues like this
Organizations commonly detect this class of issue through:
- Static analysis and route reviews that identify sensitive endpoints without authentication middleware
- Code review checks confirming authentication occurs before request dispatch or processing
- API inventories that flag network-facing endpoints lacking documented access controls
- Web application firewall or gateway policies requiring authentication for transport-layer routes
- Network and application logs showing requests to
/friend/processfrom untrusted sources - Automated security testing that verifies protected endpoints reject unauthenticated requests

