| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in pytorch serve up to 0.10.x and classified as problematic. This affects an unknown function. This manipulation causes exposure of resource. The identification of this vulnerability is CVE-2024-35199. The attack needs to be done within the local network. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability has been found in pytorch serve up to 0.10.x and classified as problematic. Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a exposure of resource vulnerability. The CWE definition for the vulnerability is CWE-668. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. As an impact it is known to affect availability. The summary by CVE is:
TorchServe is a flexible and easy-to-use tool for serving and scaling PyTorch models in production. In affected versions the two gRPC ports 7070 and 7071, are not bound to [localhost](http://localhost/) by default, so when TorchServe is launched, these two interfaces are bound to all interfaces. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are not affected. This issue in TorchServe has been fixed in PR #3083. TorchServe release 0.11.0 includes the fix to address this vulnerability. Users are advised to upgrade. There are no known workarounds for this vulnerability.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2024-35199 since 05/10/2024. The exploitation appears to be easy. The attack needs to be done within the local network. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 0.11.0 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
Website
- Product: https://github.com/pytorch/serve/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.2
CNA Vector (GitHub_M): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Exposure of resourceCWE: CWE-668 / CWE-200 / CWE-284
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: serve 0.11.0
Patch: github.com
Timeline
05/10/2024 🔍07/19/2024 🔍
07/19/2024 🔍
09/04/2025 🔍
Sources
Product: github.comAdvisory: GHSA-hhpg-v63p-wp7w
Status: Confirmed
CVE: CVE-2024-35199 (🔍)
GCVE (CVE): GCVE-0-2024-35199
GCVE (VulDB): GCVE-100-271939
Entry
Created: 07/19/2024 08:43Updated: 09/04/2025 18:00
Changes: 07/19/2024 08:43 (65), 07/19/2024 15:21 (1), 09/04/2025 18:00 (8)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.