PYSEC-2024-249
Vulnerability from pysec - Published: 2024-02-22 22:15 - Updated: 2025-05-19 11:22Summary
On all Label Studio versions prior to 1.11.0, data imported via file upload feature is not properly sanitized prior to being rendered within a Choices or Labels tag, resulting in an XSS vulnerability.
Details
Need permission to use the "data import" function. This was reproduced on Label Studio 1.10.1.
PoC
-
Create a project.
-
Upload a file containing the payload using the "Upload Files" function.
The following are the contents of the files used in the PoC
{
"data": {
"prompt": "labelstudio universe image",
"images": [
{
"value": "id123#0",
"style": "margin: 5px",
"html": "<img width='400' src='https://labelstud.io/_astro/images-tab.64279c16_ZaBSvC.avif' onload=alert(document.cookie)>"
}
]
}
}
-
Select the text-to-image generation labeling template of Ranking and scoring
-
Select a task
-
Check that the script is running
Impact
Malicious scripts can be injected into the code, and when linked with vulnerabilities such as CSRF, it can cause even greater damage. In particular, It can become a source of further attacks, especially when linked to social engineering.
| Name | purl | label-studio | pkg:pypi/label-studio |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "label-studio",
"purl": "pkg:pypi/label-studio"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5df9ae3828b98652e9fa290a19f4deedf51ef6c8"
},
{
"fixed": "5df9ae3828b98652e9fa290a19f4deedf51ef6c8"
}
],
"repo": "https://github.com/humansignal/label-studio",
"type": "GIT"
},
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.11.0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.4.1",
"0.4.2",
"0.4.3",
"0.4.4",
"0.4.4.post1",
"0.4.4.post2",
"0.4.5",
"0.4.6",
"0.4.6.post1",
"0.4.6.post2",
"0.4.7",
"0.4.8",
"0.5.0",
"0.5.1",
"0.6.0",
"0.6.1",
"0.7.0",
"0.7.1",
"0.7.2",
"0.7.3",
"0.7.4",
"0.7.4.post0",
"0.7.4.post1",
"0.7.5.post1",
"0.7.5.post2",
"0.8.0",
"0.8.0.post0",
"0.8.1",
"0.8.1.post0",
"0.8.2",
"0.8.2.post0",
"0.9.0",
"0.9.0.post2",
"0.9.0.post3",
"0.9.0.post4",
"0.9.0.post5",
"0.9.1",
"0.9.1.post0",
"0.9.1.post1",
"0.9.1.post2",
"1.0.0",
"1.0.0.post0",
"1.0.0.post1",
"1.0.0.post2",
"1.0.0.post3",
"1.0.1",
"1.0.2",
"1.0.2.post0",
"1.1.0",
"1.1.0rc0",
"1.1.1",
"1.10.0",
"1.10.0.post0",
"1.10.1",
"1.2",
"1.3",
"1.3.post0",
"1.3.post1",
"1.4",
"1.4.1",
"1.4.1.post0",
"1.4.1.post1",
"1.5.0",
"1.5.0.post0",
"1.6.0",
"1.7.0",
"1.7.1",
"1.7.2",
"1.7.3",
"1.8.0",
"1.8.1",
"1.8.2",
"1.8.2.post0",
"1.8.2.post1",
"1.9.0",
"1.9.1",
"1.9.1.post0",
"1.9.2",
"1.9.2.post0"
]
}
],
"aliases": [
"CVE-2024-26152"
],
"details": "### Summary\nOn all Label Studio versions prior to 1.11.0, data imported via file upload feature is not properly sanitized prior to being rendered within a [`Choices`](https://labelstud.io/tags/choices) or [`Labels`](https://labelstud.io/tags/labels) tag, resulting in an XSS vulnerability.\n\n### Details\nNeed permission to use the \"data import\" function. This was reproduced on Label Studio 1.10.1.\n\n### PoC\n\n1. Create a project.\n\n\n2. Upload a file containing the payload using the \"Upload Files\" function.\n\n\n\nThe following are the contents of the files used in the PoC\n```\n{\n \"data\": {\n \"prompt\": \"labelstudio universe image\",\n \"images\": [\n {\n \"value\": \"id123#0\",\n \"style\": \"margin: 5px\",\n \"html\": \"\u003cimg width=\u0027400\u0027 src=\u0027https://labelstud.io/_astro/images-tab.64279c16_ZaBSvC.avif\u0027 onload=alert(document.cookie)\u003e\"\n }\n ]\n }\n}\n```\n\n3. Select the text-to-image generation labeling template of Ranking and scoring\n\n\n\n4. Select a task\n\n\n5. Check that the script is running\n\n\n### Impact\nMalicious scripts can be injected into the code, and when linked with vulnerabilities such as CSRF, it can cause even greater damage. In particular, It can become a source of further attacks, especially when linked to social engineering.\n",
"id": "PYSEC-2024-249",
"modified": "2025-05-19T11:22:35.312280+00:00",
"published": "2024-02-22T22:15:47+00:00",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/HumanSignal/label-studio/security/advisories/GHSA-6xv9-957j-qfhg"
},
{
"type": "EVIDENCE",
"url": "https://github.com/HumanSignal/label-studio/security/advisories/GHSA-6xv9-957j-qfhg"
},
{
"type": "FIX",
"url": "https://github.com/HumanSignal/label-studio/commit/5df9ae3828b98652e9fa290a19f4deedf51ef6c8"
},
{
"type": "FIX",
"url": "https://github.com/HumanSignal/label-studio/pull/5232"
},
{
"type": "WEB",
"url": "https://github.com/HumanSignal/label-studio/releases/tag/1.11.0"
}
],
"related": [
"GHSA-6xv9-957j-qfhg",
"GHSA-6xv9-957j-qfhg"
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.