pytorch TorchServe up to 0.8.1 server-side request forgery

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.5$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in pytorch TorchServe up to 0.8.1. Affected by this issue is some unknown functionality. The manipulation leads to server-side request forgery. This vulnerability is uniquely identified as CVE-2023-43654. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in pytorch TorchServe up to 0.8.1. It has been rated as critical. This issue affects an unknown functionality. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was disclosed 09/29/2023 as GHSA-8fxr-qfr9-p34w. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-43654 since 09/20/2023. Neither technical details nor an exploit are publicly available.

Upgrading to version 0.8.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.6
VulDB Meta Temp Score: 8.5

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 10.0
CNA Vector (GitHub, Inc.): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Server-side request forgery
CWE: CWE-918
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: TorchServe 0.8.2
Patch: github.com

Timelineinfo

09/20/2023 🔍
09/29/2023 +9 days 🔍
09/29/2023 +0 days 🔍
10/04/2023 +5 days 🔍

Sourcesinfo

Advisory: GHSA-8fxr-qfr9-p34w
Status: Confirmed

CVE: CVE-2023-43654 (🔍)
GCVE (CVE): GCVE-0-2023-43654
GCVE (VulDB): GCVE-100-240857

Entryinfo

Created: 09/29/2023 07:05
Updated: 10/04/2023 09:55
Changes: 09/29/2023 07:05 (51), 10/04/2023 09:55 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

 Anonymous User (+0)
3 years ago
Goodmorning,
Can you align to the official NVD NIST cpe "pytorch:torchserve"?
Best Regards,
TEAM CERT
 VulDB Community Team3 years ago
Thank you. We have added this CPE as well. However, this CPE is not yet official part of the NIST CPE Dictionary: https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=torchserve&status=FINAL%2CDEPRECATED
 Anonymous User (+0)
3 years ago
It's right. The cpe is not the official one, I cannot find it in the CPE dictionary but in the following affected software configurations known at this link: https://nvd.nist.gov/vuln/detail/CVE-2023-43654.
Would you propose a further CPE?
 VulDB Community Team3 years ago
Good question. We assume that this CPE is going to be added to the dictionary. If it will be changed, we will update our entry as well.
 Anonymous User (+0)
3 years ago
OK.
Well, now I have a question for You: "Do you think that torchserve and sas-torch package are the same thing? If I use this package I need torchserve?
Thank You.
Best Regards,
TEAM CERT
 VulDB Community Team3 years ago
Unfortunately, we don't know at the moment. At first glance it doesn't look like it is.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!