Browse / AI Framework and Platform Flaws / CVE-2025-25297
Label Studio allows Server-Side Request Forgery in the S3 Storage Endpoint
- Class
- AI Framework and Platform Flaws (filed by a model that read the advisory)
- Technique
- Server-side request forgery
- Affected
- label-studio (PyPI)
- CVSS
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
- EPSS
- 0.7% chance of exploitation in 30 days
How it works, in short
A user-supplied S3 endpoint is passed unvalidated to the AWS SDK, so the server sends requests to internal hosts and echoes their responses in errors. (Our summary, written by a model. The source text is below.)
Details
Description
Label Studio's S3 storage integration feature contains a Server-Side Request Forgery (SSRF) vulnerability in its endpoint configuration. When creating an S3 storage connection, the application allows users to specify a custom S3 endpoint URL via the s3_endpoint parameter. This endpoint URL is passed directly to the boto3 AWS SDK without proper validation or restrictions on the protocol or destination.
The vulnerability allows an attacker to make the application send HTTP requests to arbitrary internal services by specifying them as the S3 endpoint. When the storage sync operation is triggered, the application attempts to make S3 API calls to the specified endpoint, effectively making HTTP requests to the target service and returning the response in error messages.
This SSRF vulnerability enables attackers to bypass network segmentation and access internal services that should not be accessible from the external network. The vulnerability is particularly severe because error messages from failed requests contain the full response body, allowing data exfiltration from internal services.
Steps to reproduce
1. Create an account in Label Studio
- Create a new project with basic configuration
- Create an S3 storage connection with the following configuration: