CVE-2026-3270
Server-Side Request Forgery in psi-probe Whois Component
Publication date: 2026-02-27
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 |
|---|---|---|
| psi-probe | psi_probe | to 5.3.0 (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?
CVE-2026-3270 is a Server-Side Request Forgery (SSRF) vulnerability found in psi-probe PSI Probe versions up to 5.3.0, specifically in the whois lookup functionality.
The vulnerability occurs because the application automatically follows ReferralServer responses in whois queries without validating whether the target server is trusted. This means the server can be tricked into making unauthorized requests to arbitrary or internal servers.
Technically, the flaw exists in the lookup function within the file psi-probe-core/src/main/java/psiprobe/tools/Whois.java. When a whois query returns a ReferralServer header, the application parses it and connects to the specified host and port without verifying if it is safe or authorized.
This vulnerability is remotely exploitable and a public proof-of-concept exploit is available.
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': 'This SSRF vulnerability can impact confidentiality, integrity, and availability of your systems.'}, {'type': 'list_item', 'content': 'Confidentiality: Attackers can scan internal networks, access internal services such as databases and administrative interfaces, and potentially exfiltrate sensitive information.'}, {'type': 'list_item', 'content': "Integrity: Attackers can interact with internal services using the application server's trusted identity, potentially modifying data or performing unauthorized actions."}, {'type': 'list_item', 'content': 'Availability: Excessive scanning or malicious requests may degrade the performance of the application server or internal services, causing denial of service.'}, {'type': 'paragraph', 'content': 'Additionally, attackers can bypass firewall restrictions by making the server initiate connections to internal or protected network resources.'}] [1, 2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
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 Psi Probe whois endpoint, specifically the `/whois.ajax?ip=<user_query>` endpoint, which is the entry point for exploitation.
Detection involves looking for unusual or unauthorized outbound connections initiated by the application server to internal or unexpected external IP addresses and ports, especially those triggered by whois queries.
Since the vulnerability involves the server following ReferralServer responses without validation, commands to monitor network connections or logs for such behavior can help detect exploitation attempts.
- Use network monitoring tools (e.g., tcpdump, Wireshark) to capture outbound connections from the application server to unusual IP addresses or ports.
- Check application logs for requests to `/whois.ajax` with suspicious or unexpected IP parameters.
- Example tcpdump command to monitor outbound connections on the server: `tcpdump -i eth0 host not <trusted_whois_servers> and dst port not 43` (adjust interface and ports as needed).
- Use netstat or ss commands to identify active connections initiated by the Psi Probe process: `netstat -plant | grep java` or `ss -plant | grep java`.
- Review firewall logs for outbound connection attempts from the application server to internal IP ranges or unusual ports.
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': "Immediate mitigation steps include restricting or disabling the vulnerable functionality and limiting the server's ability to make unauthorized outbound connections."}, {'type': 'list_item', 'content': 'Implement a whitelist of trusted whois servers (e.g., whois.arin.net, whois.iana.org) and block referrals to untrusted servers before following them.'}, {'type': 'list_item', 'content': 'Disable or comment out the code that follows ReferralServer responses in the whois lookup functionality, as this is not essential for core whois operations.'}, {'type': 'list_item', 'content': 'Restrict outbound network connections from the application server using firewall rules or network segmentation to only allow necessary destinations.'}, {'type': 'list_item', 'content': 'Consider replacing the affected Psi Probe component with an alternative product, as no official patches or countermeasures are available from the vendor.'}, {'type': 'paragraph', 'content': 'These steps help prevent attackers from exploiting the SSRF vulnerability to scan internal networks, access internal services, or bypass firewall restrictions.'}] [1, 3]