Xbow-Security

#2894of 60,753
99.9Total CVSS
Vulnerabilities · 13
Medium
6
High
6
Critical
1
PT-2025-7074
2025-02-14
8.7
CVE-2025-25295
Unknown
Label Studio Sdk
Name of the Vulnerable Software and Affected Versions: Label Studio versions prior to 1.16.0 Label Studio SDK versions prior to 1.0.10 Description: A path traversal vulnerability in Label Studio SDK allows unauthorized file access outside the intended directory structure. The flaw exists in the VOC, COCO, and YOLO export functionalities, which invoke a `download` function on the `label-studio-sdk` python package that fails to validate file paths when processing image references during task exports. By creating tasks with path traversal sequences in the image field, an attacker can force the application to read files from arbitrary server filesystem locations when exporting projects in any of the mentioned formats. This is an authentication-required vulnerability allowing arbitrary file reads from the server filesystem, potentially exposing sensitive information like configuration files, credentials, and confidential data. Recommendations: To mitigate this issue, Label Studio users should upgrade to version 1.16.0 or newer. As a temporary workaround, consider validating and sanitizing file paths, adding an allowlist of directories and file types, implementing file access controls, and using randomized file names and secure file storage abstraction. Restrict access to the vulnerable `download` function in the `label-studio-sdk` python package to minimize the risk of exploitation. Avoid using the `image` field in the affected API endpoint until the issue is resolved.
PT-2025-7076
2025-02-14
8.6
CVE-2025-25297
Unknown
Label Studio
Name of the Vulnerable Software and Affected Versions: Label Studio versions prior to 1.16.0 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. Recommendations: To resolve the issue, update to version 1.16.0 or later, which contains a patch for the SSRF vulnerability. As a temporary workaround, consider implementing strict validation of S3 endpoint URLs to allow only valid S3 service endpoints, adding an allowlist of endpoint domains and protocols, and sanitizing error messages to prevent leakage of sensitive information from failed requests. Additionally, consider implementing network-level controls to restrict outbound connections from the application server.