S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Network Vulnerabilities·Updated Oct 8, 2024

CVE-2023-43654 Scanner

CVE-2023-43654 Scanner - Server-Side-Request-Forgery (SSRF) vulnerability in TorchServe

Est. Time~1 minutes
Scan TypeSingle Scan
Targetsdomain, ipv4, subdomain
CostFree
2.1k
Times Used
continuous scan runs
4.8k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2023-43654
9.8
CVSScritical
Exploitable remotely over the internet · no authentication required.

TorchServe is a tool for serving and scaling PyTorch models in production. TorchServe default configuration lacks proper input validation, enabling third parties to invoke remote HTTP download requests and write files to the disk. This issue could be taken advantage of to compromise the integrity of the system and sensitive data. This issue is present in versions 0.1.0 to 0.8.1. A user is able to load the model of their choice from any URL that they would like to use. The user of TorchServe is responsible for configuring both the allowed_urls and specifying the model URL to be used. A pull request to warn the user when the default value for allowed_urls is used has been merged in PR #2534. TorchServe release 0.8.2 includes this change. Users are advised to upgrade. There are no known workarounds for this issue.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
serveby pytorch
>= 0.1.0, < 0.8.2
torchserveby pytorch
AFFECTED< 0.8.2SAFE ✓≥ 0.8.2
Updated Aug 22, 2026View on NVD →
Detail

TorchServe is a robust tool widely used in production environments for serving and scaling PyTorch models. It is utilized by data scientists and developers for deploying machine learning models. PyTorch is often employed in academic research and commercial applications due to its dynamic computation capabilities. TorchServe allows users to import and serve trained models efficiently within their infrastructure. It provides scalability to handle large volumes of requests, making it suitable for industrial-scale applications. The tool fosters an easy integration with other services and platforms, enhancing workflow efficiency in AI model deployment.

The vulnerability in question is a Server-Side-Request-Forgery (SSRF) flaw found in TorchServe. This critical issue arises due to inadequate input validation in the default configuration. It allows external parties to execute HTTP requests remotely and potentially manipulate saved data. The vulnerability exists due to insufficient restrictions on URL inputs meant for model loading, leaving the system exposed to unauthorized external requests. Exploiting this SSRF vulnerability could lead to unauthorized actions being performed on the affected server. The problem is prevalent in TorchServe versions ranging from 0.1.0 to 0.8.1.

TorchServe's SSRF vulnerability allows attackers to trick the server into making unwanted requests to an unintended location. This is facilitated through insufficient validation of user-supplied input for model URLs. Due to this, a malicious user can manipulate the model loading mechanism to request URLs that serve an attacker's purpose. The successful exploitation of this vulnerability could lead to data exposure or data manipulation. TorchServe lacks the ability to distinguish between authorized and unauthorized network resources effectively. Users must ensure scrutinized configuration settings to mitigate the potential misuse.

Exploitation of this vulnerability could compromise sensitive data and the integrity of the entire system. Attackers could misuse the SSRF flaw to escalate their privileges or even perform data exfiltration. Moreover, unauthorized access to network resources can lead to service disruptions or the execution of unauthorized operations. There is the possibility of subsequent internal attacks due to obtained internal network details. Some extreme consequences may include affecting the overall availability and reliability of TorchServe applications. As the system's boundary is bypassed, it raises significant security concerns requiring prompt corrective measures.

REFERENCES

Solution Advice
  • Upgrade TorchServe to the latest version, as the issue is resolved in version 0.8.2 and above.
  • Implement strict URL input validation and restrict permitted domains through the allowed_urls setting.
  • Ensure that firewall rules are in place to limit server's outgoing requests to trusted domains only.
  • Review and adjust model hosting configurations to avoid exposure to external influence.
  • Audit existing deployed instances for any anomalies or unauthorized changes.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.