CVE-2025-14518
BaseFortify
Publication date: 2025-12-11
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| powerjob | powerjob | to 5.1.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in PowerJob up to version 5.1.2, specifically in the checkConnectivity function of the Network Request Handler component. It involves manipulation of the targetIp or targetPort arguments, which leads to server-side request forgery (SSRF). This means an attacker can make the server send unauthorized requests to other systems, potentially exploiting internal network resources. The vulnerability can be exploited remotely and the exploit is publicly available.
How can this vulnerability impact me? :
The vulnerability can allow an attacker to perform server-side request forgery, enabling them to make the affected server send unauthorized requests to internal or external systems. This can lead to unauthorized access to internal services, data leakage, or further exploitation of internal network resources, potentially compromising the security and integrity of your systems.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring and analyzing requests to the `/server/checkConnectivity` endpoint, specifically looking for unusual or unauthorized usage of the `targetIp` and `targetPort` parameters. You can detect exploitation attempts by capturing HTTP GET requests with these parameters targeting internal IP addresses or unexpected ports. Additionally, network traffic logs can be inspected for outbound connections initiated by the server to internal or attacker-controlled hosts. A practical detection method is to use network monitoring tools or web server logs to identify requests to `/server/checkConnectivity` with suspicious parameters. For example, using curl to test the endpoint: `curl -G 'http://<powerjob-server>/server/checkConnectivity' --data-urlencode 'targetIp=<internal-ip-or-malicious-ip>' --data-urlencode 'targetPort=<port>'` and observing the server response or network behavior. Also, monitoring outbound connections from the server to unexpected destinations can help detect exploitation. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable `/server/checkConnectivity` endpoint by implementing network-level controls such as firewall rules or access control lists to limit who can reach this endpoint. Disable or restrict the functionality if possible until a patch or update is available. Since no known countermeasures or mitigations have been identified in the affected versions, consider replacing or upgrading the affected PowerJob component to a version that addresses this vulnerability once available. Additionally, monitor logs for suspicious activity and block any detected exploitation attempts. If feasible, implement input validation or filtering on the `targetIp` and `targetPort` parameters to prevent unauthorized internal network requests. [3, 2]