CVE-2024-35198: TorchServe bypass allowed_urls configuration

Published Jul 18, 2024
·
Updated

Impact TorchServe's check on allowedurls configuration can be by-passed if the URL contains characters such as ".." but it does not prevent the model from being downloaded into the model store. Once a file is downloaded, it can be referenced without providing a URL the second time, which effectively bypasses the allowedurls security check. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are not affected.

Patches This issue in TorchServe has been fixed by validating the URL without characters such as ".." before downloading: #3082.

TorchServe release 0.11.0 includes the fix to address this vulnerability.

References #3082 TorchServe release v0.11.0

Thank Kroll Cyber Risk for for responsibly disclosing this issue.

If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.

Other sources

TorchServe is a flexible and easy-to-use tool for serving and scaling PyTorch models in production. TorchServe 's check on allowedurls configuration can be by-passed if the URL contains characters such as ".." but it does not prevent the model from being downloaded into the model store. Once a file is downloaded, it can be referenced without providing a URL the second time, which effectively bypasses the allowedurls security check. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are not affected. This issue in TorchServe has been fixed by validating the URL without characters such as ".." before downloading see PR #3082. 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.

MITRE

Affected Software

2 affected componentsFixes available
pip/torchserve<0.11.0
0.11.0
PyTorch Torchserve>=0.4.2<0.11.0

Event History

Jul 18, 2024
Advisory Published
via GitHub·10:03 PM
CVE Published
via MITRE·10:40 PM
Data Sourced
via MITRE·10:40 PM
DescriptionSeverityWeakness
Jul 19, 2024
Data Sourced
via NVD·02:15 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 AM
RemedyAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-35198?

CVE-2024-35198 is classified as a medium severity vulnerability.

2

How do I fix CVE-2024-35198?

To fix CVE-2024-35198, upgrade to torchserve version 0.11.0 or later.

3

What specifically does CVE-2024-35198 impact?

CVE-2024-35198 impacts the allowed_urls configuration in TorchServe, allowing bypass for certain URL formats.

4

Can the vulnerability CVE-2024-35198 lead to unauthorized access?

Yes, CVE-2024-35198 can potentially lead to unauthorized model downloads into the model store.

5

Is there a specific character that triggers CVE-2024-35198?

Yes, certain characters such as '..' in URLs can bypass checks defined in CVE-2024-35198.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203