Benchmark data exposure via unverified S3 destination
Published Mar 20, 2025 · Updated Mar 20, 2025
Business logic error in TorchServe 0.11.0 and earlier allows remote attackers to receive benchmark results through an unverified S3 bucket. The upload_results_to_s3.sh script hardcodes benchmarkai-metrics-prod and recursively copies every output directory without verifying destination ownership or access. Exploitation requires an operator to run the script with AWS access while the bucket is attacker-controlled, exposing the uploaded benchmark output.
Summary
What happened
Business logic error in TorchServe 0.11.0 and earlier allows remote attackers to receive benchmark results through an unverified S3 bucket. The upload_results_to_s3.sh script hardcodes benchmarkai-metrics-prod and recursively copies every output directory without verifying destination ownership or access. Exploitation requires an operator to run the script with AWS access while the bucket is attacker-controlled, exposing the uploaded benchmark output.
The record
- CVE
- CVE-2024-6577
- Published
- Mar 20, 2025
- Updated
- Mar 20, 2025
- Vendor
- PyTorch
- Product
- TorchServe
- Classifications
- CWE-840, T1567.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2025CVE publishedPublication date reported by the CVE source.
- Mar 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=latest
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo