@blamejs/exceptd-skills 0.13.108 → 0.13.109
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +4 -0
- package/data/_indexes/_meta.json +9 -9
- package/data/_indexes/activity-feed.json +2 -2
- package/data/_indexes/catalog-summaries.json +2 -2
- package/data/_indexes/chains.json +476 -0
- package/data/atlas-ttps.json +2 -0
- package/data/attack-techniques.json +5 -0
- package/data/cve-catalog.json +207 -0
- package/data/cwe-catalog.json +2 -0
- package/data/framework-control-gaps.json +18 -0
- package/data/zeroday-lessons.json +100 -0
- package/manifest.json +44 -44
- package/package.json +2 -2
- package/sbom.cdx.json +25 -25
package/data/cve-catalog.json
CHANGED
|
@@ -17090,6 +17090,213 @@
|
|
|
17090
17090
|
"_intake_method": "manual-verified-curation",
|
|
17091
17091
|
"_kev_short_description": "Label Studio's Data Import fetches user-supplied URLs without restriction (self-registration on by default), letting a remote attacker read files / reach internal services via the server (CWE-918 SSRF); fixed in 1.6.0."
|
|
17092
17092
|
},
|
|
17093
|
+
"CVE-2023-47117": {
|
|
17094
|
+
"name": "Label Studio ORM Filter Manipulation Sensitive-Field Disclosure",
|
|
17095
|
+
"type": "Information Disclosure",
|
|
17096
|
+
"cvss_score": 7.5,
|
|
17097
|
+
"cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
|
|
17098
|
+
"cvss_note": "GitHub (CNA) CVSS v3.1 base 7.5 (HIGH, confidentiality-only); NVD has not published its own assessed score. Label Studio lets users set task filters that are passed into a Django ORM query without restriction, so an attacker manipulates the filter to read sensitive fields (including password hashes and tokens) from all user accounts (CWE-200 information exposure).",
|
|
17099
|
+
"cisa_kev": false,
|
|
17100
|
+
"poc_available": true,
|
|
17101
|
+
"poc_description": "Documented in the disclosing advisory (https://github.com/advisories/GHSA-6hjj-gq77-j4qw); manipulate the task filter to read password hashes/tokens from all accounts.",
|
|
17102
|
+
"ai_discovered": false,
|
|
17103
|
+
"ai_discovery_source": "human_researcher",
|
|
17104
|
+
"ai_discovery_notes": "Disclosed via the GitHub Security Advisory (https://github.com/advisories/GHSA-6hjj-gq77-j4qw). The abused surface is Label Studio, a widely used data-labeling / annotation platform in ML pipelines.",
|
|
17105
|
+
"ai_assisted_weaponization": false,
|
|
17106
|
+
"ai_assisted_notes": "No AI-assisted weaponization; the flaw is broken object-level authorization / sensitive-field exposure in an ML data-platform API.",
|
|
17107
|
+
"active_exploitation": "none",
|
|
17108
|
+
"active_exploitation_notes": "Advisory disclosure with a coordinated fix; no confirmed in-the-wild exploitation reported as of curation.",
|
|
17109
|
+
"affected": "Label Studio before 1.9.2post0.",
|
|
17110
|
+
"affected_versions": [
|
|
17111
|
+
"Label Studio < 1.9.2post0"
|
|
17112
|
+
],
|
|
17113
|
+
"vector": "Label Studio's task-filter feature passes user-controlled filter expressions into a Django ORM query without restricting which fields can be referenced. An attacker crafts a filter that selects sensitive columns (password hashes, auth tokens) across all user accounts and reads them back - a sensitive-field exposure via ORM manipulation (CWE-200) that supplies the material to forge sessions and impersonate users.",
|
|
17114
|
+
"complexity": "low",
|
|
17115
|
+
"complexity_notes": "GitHub CNA AV:N / AC:L / PR:N - unauthenticated field disclosure.",
|
|
17116
|
+
"patch_available": true,
|
|
17117
|
+
"patch_required_reboot": false,
|
|
17118
|
+
"live_patch_available": false,
|
|
17119
|
+
"live_patch_tools": [],
|
|
17120
|
+
"live_patch_notes": "Remediation is upgrading to 1.9.2post0 or later; redeploy, no host reboot.",
|
|
17121
|
+
"vendor_update_paths": [
|
|
17122
|
+
"Upgrade Label Studio to 1.9.2post0 or later. Enforce object-level authorization and serializer field allowlists on the API (never let user-controlled filters or responses expose secrets, tokens, or other users' fields), and rotate any exposed session-signing secrets / credentials."
|
|
17123
|
+
],
|
|
17124
|
+
"framework_control_gaps": {
|
|
17125
|
+
"NIST-800-53-AC-3": "Access enforcement does not constrain which records/fields a user can read - a user-controlled ORM filter reads other accounts' sensitive fields.",
|
|
17126
|
+
"NIST-800-53-SC-28": "Protection of information at rest is insufficient: sensitive fields (password hashes, tokens) are readable through the API and directly usable once leaked.",
|
|
17127
|
+
"ISO-27001-2022-A.5.15": "Access control does not enforce object-level authorization on the ML data-platform API.",
|
|
17128
|
+
"NIS2-Art21-identity-management": "Identity/access measures do not prevent API-level sensitive-field exposure from enabling account impersonation.",
|
|
17129
|
+
"DORA-Art-9": "ICT protection measures do not model API sensitive-field exposure / account takeover of an ML platform as an ICT-risk event.",
|
|
17130
|
+
"UK-CAF-B2": "Identity and Access Control objective has no objective for object-level authorization on AI data-platform APIs.",
|
|
17131
|
+
"UK-CAF-B4": "System Security objective has no objective for serializer field allowlisting / ORM-filter restriction in ML platforms.",
|
|
17132
|
+
"AU-ISM-1546": "Patch-application control does not single out ML data-labeling platforms.",
|
|
17133
|
+
"ALL-AI-PIPELINE-INTEGRITY": "No framework treats an ML data-platform API's object-level authorization and sensitive-field exposure as integrity controls whose failure yields account takeover."
|
|
17134
|
+
},
|
|
17135
|
+
"atlas_refs": [
|
|
17136
|
+
"AML.T0049"
|
|
17137
|
+
],
|
|
17138
|
+
"attack_refs": [
|
|
17139
|
+
"T1190",
|
|
17140
|
+
"T1552"
|
|
17141
|
+
],
|
|
17142
|
+
"rwep_score": 23,
|
|
17143
|
+
"rwep_factors": {
|
|
17144
|
+
"cisa_kev": 0,
|
|
17145
|
+
"poc_available": 20,
|
|
17146
|
+
"ai_factor": 0,
|
|
17147
|
+
"active_exploitation": 0,
|
|
17148
|
+
"blast_radius": 18,
|
|
17149
|
+
"patch_available": -15,
|
|
17150
|
+
"live_patch_available": 0,
|
|
17151
|
+
"reboot_required": 0
|
|
17152
|
+
},
|
|
17153
|
+
"rwep_notes": "Moderate (RWEP 23, \"patch within 30 days\" band per lib/scoring.js timeline). Not KEV, no confirmed in-the-wild exploitation, patched at disclosure (Hard Rule #3): poc_available=20 + blast_radius=18, minus patch_available 15. This is the first half of a Label Studio privilege-escalation chain - the ORM sensitive-field leak (CVE-2023-47117) supplies the material the impersonation flaw (CVE-2023-43791) replays.",
|
|
17154
|
+
"epss_score": null,
|
|
17155
|
+
"epss_date": "2026-05-25",
|
|
17156
|
+
"epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
|
|
17157
|
+
"epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2023-47117",
|
|
17158
|
+
"cwe_refs": [
|
|
17159
|
+
"CWE-200"
|
|
17160
|
+
],
|
|
17161
|
+
"iocs": {
|
|
17162
|
+
"behavioral": [
|
|
17163
|
+
"Label Studio task-filter requests referencing sensitive columns (password hashes, tokens) or other users' fields.",
|
|
17164
|
+
"API responses returning sensitive fields from accounts other than the requester's.",
|
|
17165
|
+
"Label Studio < 1.9.2post0 with the task-filter API reachable - the exposed precondition."
|
|
17166
|
+
],
|
|
17167
|
+
"_ioc_source_note": "Behavioral signatures anchored to the GitHub Security Advisory (https://github.com/advisories/GHSA-6hjj-gq77-j4qw) and NVD CVE-2023-47117 (CWE-200)."
|
|
17168
|
+
},
|
|
17169
|
+
"source_verified": "2026-05-25",
|
|
17170
|
+
"verification_sources": [
|
|
17171
|
+
"https://nvd.nist.gov/vuln/detail/CVE-2023-47117",
|
|
17172
|
+
"https://github.com/advisories/GHSA-6hjj-gq77-j4qw"
|
|
17173
|
+
],
|
|
17174
|
+
"vendor_advisories": [
|
|
17175
|
+
{
|
|
17176
|
+
"vendor": "GitHub Security Advisory",
|
|
17177
|
+
"advisory_id": "CVE-2023-47117",
|
|
17178
|
+
"url": "https://github.com/advisories/GHSA-6hjj-gq77-j4qw",
|
|
17179
|
+
"severity": "high",
|
|
17180
|
+
"published_date": "2023-11-14"
|
|
17181
|
+
},
|
|
17182
|
+
{
|
|
17183
|
+
"vendor": "NVD",
|
|
17184
|
+
"advisory_id": "CVE-2023-47117",
|
|
17185
|
+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-47117",
|
|
17186
|
+
"severity": "high",
|
|
17187
|
+
"published_date": "2023-11-14"
|
|
17188
|
+
}
|
|
17189
|
+
],
|
|
17190
|
+
"last_updated": "2026-05-25",
|
|
17191
|
+
"discovery_attribution_note": "Manually curated from the GitHub Security Advisory (https://github.com/advisories/GHSA-6hjj-gq77-j4qw, CWE-200) + NVD (CVSS v3.1 7.5). Label Studio privilege-escalation chain (47117 ORM leak -> 43791 impersonation); introduces the AI-app API object-authorization / field-exposure control NEW-CTRL-106.",
|
|
17192
|
+
"_auto_imported": false,
|
|
17193
|
+
"_intake_method": "manual-verified-curation",
|
|
17194
|
+
"_kev_short_description": "Label Studio's task-filter feature passes user input into a Django ORM query unrestricted, leaking sensitive fields (password hashes, tokens) from all accounts (CWE-200); fixed in 1.9.2post0."
|
|
17195
|
+
},
|
|
17196
|
+
"CVE-2023-43791": {
|
|
17197
|
+
"name": "Label Studio Account Impersonation and Privilege Escalation",
|
|
17198
|
+
"type": "Privilege Escalation",
|
|
17199
|
+
"cvss_score": 8.8,
|
|
17200
|
+
"cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
|
17201
|
+
"cvss_note": "NIST (NVD) CVSS v3.1 base 8.8 (HIGH, PR:L); the GitHub (CNA) advisory rates it 9.8 (CRITICAL, PR:N). Label Studio exposes information that lets an attacker impersonate any account and escalate from a low-privilege user to a Django super administrator - chained with the ORM sensitive-field leak (CVE-2023-47117), the exposed secrets/tokens are used to forge authenticated sessions (CWE-200).",
|
|
17202
|
+
"cisa_kev": false,
|
|
17203
|
+
"poc_available": true,
|
|
17204
|
+
"poc_description": "Documented in the disclosing advisory (https://github.com/advisories/GHSA-f475-x83m-rx5m); chain the ORM leak to forge a session and impersonate / escalate to superadmin.",
|
|
17205
|
+
"ai_discovered": false,
|
|
17206
|
+
"ai_discovery_source": "human_researcher",
|
|
17207
|
+
"ai_discovery_notes": "Disclosed via the GitHub Security Advisory (https://github.com/advisories/GHSA-f475-x83m-rx5m). The abused surface is Label Studio, a widely used data-labeling / annotation platform in ML pipelines.",
|
|
17208
|
+
"ai_assisted_weaponization": false,
|
|
17209
|
+
"ai_assisted_notes": "No AI-assisted weaponization; the flaw is broken object-level authorization / sensitive-field exposure in an ML data-platform API.",
|
|
17210
|
+
"active_exploitation": "none",
|
|
17211
|
+
"active_exploitation_notes": "Advisory disclosure with a coordinated fix; no confirmed in-the-wild exploitation reported as of curation.",
|
|
17212
|
+
"affected": "Label Studio before 1.8.2.",
|
|
17213
|
+
"affected_versions": [
|
|
17214
|
+
"Label Studio < 1.8.2"
|
|
17215
|
+
],
|
|
17216
|
+
"vector": "Label Studio exposes sensitive information that, chained with the ORM sensitive-field leak (CVE-2023-47117), lets an attacker impersonate any account and escalate from a low-privilege user to a Django super administrator. The leaked secrets/tokens are used to forge authenticated sessions and take over accounts (CWE-200 leading to broken object-level authorization).",
|
|
17217
|
+
"complexity": "low",
|
|
17218
|
+
"complexity_notes": "NVD AV:N / AC:L / PR:L (GitHub CNA marks PR:N) - a low-privilege account suffices, and the chain reaches Django superadmin.",
|
|
17219
|
+
"patch_available": true,
|
|
17220
|
+
"patch_required_reboot": false,
|
|
17221
|
+
"live_patch_available": false,
|
|
17222
|
+
"live_patch_tools": [],
|
|
17223
|
+
"live_patch_notes": "Remediation is upgrading to 1.8.2 or later; redeploy, no host reboot.",
|
|
17224
|
+
"vendor_update_paths": [
|
|
17225
|
+
"Upgrade Label Studio to 1.8.2 or later. Enforce object-level authorization and serializer field allowlists on the API (never let user-controlled filters or responses expose secrets, tokens, or other users' fields), and rotate any exposed session-signing secrets / credentials."
|
|
17226
|
+
],
|
|
17227
|
+
"framework_control_gaps": {
|
|
17228
|
+
"NIST-800-53-AC-3": "Access enforcement does not constrain which records/fields a user can read - leaked material is replayed to impersonate any account.",
|
|
17229
|
+
"NIST-800-53-SC-28": "Protection of information at rest is insufficient: sensitive fields (password hashes, tokens) are readable through the API and directly usable once leaked.",
|
|
17230
|
+
"ISO-27001-2022-A.5.15": "Access control does not enforce object-level authorization on the ML data-platform API.",
|
|
17231
|
+
"NIS2-Art21-identity-management": "Identity/access measures do not prevent API-level sensitive-field exposure from enabling account impersonation.",
|
|
17232
|
+
"DORA-Art-9": "ICT protection measures do not model API sensitive-field exposure / account takeover of an ML platform as an ICT-risk event.",
|
|
17233
|
+
"UK-CAF-B2": "Identity and Access Control objective has no objective for object-level authorization on AI data-platform APIs.",
|
|
17234
|
+
"UK-CAF-B4": "System Security objective has no objective for serializer field allowlisting / ORM-filter restriction in ML platforms.",
|
|
17235
|
+
"AU-ISM-1546": "Patch-application control does not single out ML data-labeling platforms.",
|
|
17236
|
+
"ALL-AI-PIPELINE-INTEGRITY": "No framework treats an ML data-platform API's object-level authorization and sensitive-field exposure as integrity controls whose failure yields account takeover."
|
|
17237
|
+
},
|
|
17238
|
+
"atlas_refs": [
|
|
17239
|
+
"AML.T0049"
|
|
17240
|
+
],
|
|
17241
|
+
"attack_refs": [
|
|
17242
|
+
"T1190",
|
|
17243
|
+
"T1078",
|
|
17244
|
+
"T1212"
|
|
17245
|
+
],
|
|
17246
|
+
"rwep_score": 29,
|
|
17247
|
+
"rwep_factors": {
|
|
17248
|
+
"cisa_kev": 0,
|
|
17249
|
+
"poc_available": 20,
|
|
17250
|
+
"ai_factor": 0,
|
|
17251
|
+
"active_exploitation": 0,
|
|
17252
|
+
"blast_radius": 24,
|
|
17253
|
+
"patch_available": -15,
|
|
17254
|
+
"live_patch_available": 0,
|
|
17255
|
+
"reboot_required": 0
|
|
17256
|
+
},
|
|
17257
|
+
"rwep_notes": "Moderate (RWEP 29, \"patch within 30 days\" band per lib/scoring.js timeline). Not KEV, no confirmed in-the-wild exploitation, patched at disclosure (Hard Rule #3): poc_available=20 + blast_radius=24, minus patch_available 15. This is the second half of a Label Studio privilege-escalation chain - the ORM sensitive-field leak (CVE-2023-47117) supplies the material the impersonation flaw (CVE-2023-43791) replays.",
|
|
17258
|
+
"epss_score": null,
|
|
17259
|
+
"epss_date": "2026-05-25",
|
|
17260
|
+
"epss_note": "EPSS not pulled for this entry; retrieve via FIRST EPSS API in a future refresh.",
|
|
17261
|
+
"epss_source": "https://api.first.org/data/v1/epss?cve=CVE-2023-43791",
|
|
17262
|
+
"cwe_refs": [
|
|
17263
|
+
"CWE-200"
|
|
17264
|
+
],
|
|
17265
|
+
"iocs": {
|
|
17266
|
+
"behavioral": [
|
|
17267
|
+
"Authenticated sessions in Label Studio minted/used for accounts the requester should not control, or sudden escalation to Django superadmin.",
|
|
17268
|
+
"Use of leaked password hashes / tokens to forge or replay Label Studio sessions.",
|
|
17269
|
+
"Label Studio < 1.8.2 reachable by a low-privilege user - the exposed precondition for the privesc chain."
|
|
17270
|
+
],
|
|
17271
|
+
"_ioc_source_note": "Behavioral signatures anchored to the GitHub Security Advisory (https://github.com/advisories/GHSA-f475-x83m-rx5m) and NVD CVE-2023-43791 (CWE-200)."
|
|
17272
|
+
},
|
|
17273
|
+
"source_verified": "2026-05-25",
|
|
17274
|
+
"verification_sources": [
|
|
17275
|
+
"https://nvd.nist.gov/vuln/detail/CVE-2023-43791",
|
|
17276
|
+
"https://github.com/advisories/GHSA-f475-x83m-rx5m"
|
|
17277
|
+
],
|
|
17278
|
+
"vendor_advisories": [
|
|
17279
|
+
{
|
|
17280
|
+
"vendor": "GitHub Security Advisory",
|
|
17281
|
+
"advisory_id": "CVE-2023-43791",
|
|
17282
|
+
"url": "https://github.com/advisories/GHSA-f475-x83m-rx5m",
|
|
17283
|
+
"severity": "critical",
|
|
17284
|
+
"published_date": "2023-11-09"
|
|
17285
|
+
},
|
|
17286
|
+
{
|
|
17287
|
+
"vendor": "NVD",
|
|
17288
|
+
"advisory_id": "CVE-2023-43791",
|
|
17289
|
+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-43791",
|
|
17290
|
+
"severity": "high",
|
|
17291
|
+
"published_date": "2023-11-09"
|
|
17292
|
+
}
|
|
17293
|
+
],
|
|
17294
|
+
"last_updated": "2026-05-25",
|
|
17295
|
+
"discovery_attribution_note": "Manually curated from the GitHub Security Advisory (https://github.com/advisories/GHSA-f475-x83m-rx5m, CWE-200) + NVD (CVSS v3.1 8.8; GitHub CNA 9.8). Label Studio privilege-escalation chain (47117 ORM leak -> 43791 impersonation); introduces the AI-app API object-authorization / field-exposure control NEW-CTRL-106.",
|
|
17296
|
+
"_auto_imported": false,
|
|
17297
|
+
"_intake_method": "manual-verified-curation",
|
|
17298
|
+
"_kev_short_description": "Label Studio exposes information enabling account impersonation and escalation to Django superadmin (chained with the ORM leak CVE-2023-47117); CWE-200, fixed in 1.8.2."
|
|
17299
|
+
},
|
|
17093
17300
|
"CVE-2026-41091": {
|
|
17094
17301
|
"name": "Microsoft Defender (Malware Protection Engine) Link-Following LPE to SYSTEM",
|
|
17095
17302
|
"type": "LPE",
|
package/data/cwe-catalog.json
CHANGED
|
@@ -37,6 +37,8 @@
|
|
|
37
37
|
"CVE-2022-1471",
|
|
38
38
|
"CVE-2022-36551",
|
|
39
39
|
"CVE-2023-43654",
|
|
40
|
+
"CVE-2023-43791",
|
|
41
|
+
"CVE-2023-47117",
|
|
40
42
|
"CVE-2023-48022",
|
|
41
43
|
"CVE-2023-51449",
|
|
42
44
|
"CVE-2023-6016",
|
|
@@ -2198,6 +2200,8 @@
|
|
|
2198
2200
|
"opened_date": "2026-04-01",
|
|
2199
2201
|
"evidence_cves": [
|
|
2200
2202
|
"BUG-2026-NIGHTMARE-ECLIPSE-YELLOWKEY",
|
|
2203
|
+
"CVE-2023-43791",
|
|
2204
|
+
"CVE-2023-47117",
|
|
2201
2205
|
"CVE-2025-14847",
|
|
2202
2206
|
"CVE-2025-22226",
|
|
2203
2207
|
"CVE-2026-43284"
|
|
@@ -3839,6 +3843,8 @@
|
|
|
3839
3843
|
"evidence_cves": [
|
|
3840
3844
|
"CVE-2022-1471",
|
|
3841
3845
|
"CVE-2023-43654",
|
|
3846
|
+
"CVE-2023-43791",
|
|
3847
|
+
"CVE-2023-47117",
|
|
3842
3848
|
"CVE-2023-48022",
|
|
3843
3849
|
"CVE-2023-6019",
|
|
3844
3850
|
"CVE-2023-6021",
|
|
@@ -5062,7 +5068,9 @@
|
|
|
5062
5068
|
"CVE-2022-1471",
|
|
5063
5069
|
"CVE-2022-36551",
|
|
5064
5070
|
"CVE-2023-43654",
|
|
5071
|
+
"CVE-2023-43791",
|
|
5065
5072
|
"CVE-2023-44467",
|
|
5073
|
+
"CVE-2023-47117",
|
|
5066
5074
|
"CVE-2023-48022",
|
|
5067
5075
|
"CVE-2023-51449",
|
|
5068
5076
|
"CVE-2023-6016",
|
|
@@ -5178,6 +5186,8 @@
|
|
|
5178
5186
|
"opened_date": "2026-05-15",
|
|
5179
5187
|
"evidence_cves": [
|
|
5180
5188
|
"CVE-2022-36551",
|
|
5189
|
+
"CVE-2023-43791",
|
|
5190
|
+
"CVE-2023-47117",
|
|
5181
5191
|
"CVE-2023-6038",
|
|
5182
5192
|
"CVE-2024-1709",
|
|
5183
5193
|
"CVE-2025-25297",
|
|
@@ -5474,6 +5484,8 @@
|
|
|
5474
5484
|
"status": "open",
|
|
5475
5485
|
"opened_date": "2026-05-15",
|
|
5476
5486
|
"evidence_cves": [
|
|
5487
|
+
"CVE-2023-43791",
|
|
5488
|
+
"CVE-2023-47117",
|
|
5477
5489
|
"CVE-2023-6016",
|
|
5478
5490
|
"CVE-2023-6038",
|
|
5479
5491
|
"CVE-2025-3248",
|
|
@@ -5638,7 +5650,9 @@
|
|
|
5638
5650
|
"opened_date": "2026-05-17",
|
|
5639
5651
|
"evidence_cves": [
|
|
5640
5652
|
"CVE-2022-36551",
|
|
5653
|
+
"CVE-2023-43791",
|
|
5641
5654
|
"CVE-2023-44467",
|
|
5655
|
+
"CVE-2023-47117",
|
|
5642
5656
|
"CVE-2023-51449",
|
|
5643
5657
|
"CVE-2023-6016",
|
|
5644
5658
|
"CVE-2023-6038",
|
|
@@ -5741,7 +5755,9 @@
|
|
|
5741
5755
|
"CVE-2022-1471",
|
|
5742
5756
|
"CVE-2022-36551",
|
|
5743
5757
|
"CVE-2023-43654",
|
|
5758
|
+
"CVE-2023-43791",
|
|
5744
5759
|
"CVE-2023-44467",
|
|
5760
|
+
"CVE-2023-47117",
|
|
5745
5761
|
"CVE-2023-48022",
|
|
5746
5762
|
"CVE-2023-51449",
|
|
5747
5763
|
"CVE-2023-6016",
|
|
@@ -6025,6 +6041,8 @@
|
|
|
6025
6041
|
"opened_date": "2026-05-18",
|
|
6026
6042
|
"evidence_cves": [
|
|
6027
6043
|
"CVE-2020-10148",
|
|
6044
|
+
"CVE-2023-43791",
|
|
6045
|
+
"CVE-2023-47117",
|
|
6028
6046
|
"CVE-2023-48022",
|
|
6029
6047
|
"CVE-2023-6038",
|
|
6030
6048
|
"CVE-2025-3248",
|
|
@@ -4611,6 +4611,106 @@
|
|
|
4611
4611
|
"_auto_imported": false,
|
|
4612
4612
|
"_intake_method": "manual-verified-curation"
|
|
4613
4613
|
},
|
|
4614
|
+
"CVE-2023-47117": {
|
|
4615
|
+
"name": "Label Studio ORM Filter Manipulation Sensitive-Field Disclosure",
|
|
4616
|
+
"lesson_date": "2026-05-25",
|
|
4617
|
+
"attack_vector": {
|
|
4618
|
+
"description": "Label Studio passes user-controlled task filters into a Django ORM query without restricting referenced fields, so an attacker reads sensitive fields (password hashes, tokens) from all user accounts.",
|
|
4619
|
+
"privileges_required": "none (unauthenticated field disclosure)",
|
|
4620
|
+
"complexity": "low",
|
|
4621
|
+
"ai_factor": "The abused surface is Label Studio, a data-labeling / annotation platform central to ML data pipelines. The lesson: an ML data-platform API must enforce object-level authorization and never expose sensitive fields - this CVE supplies the leaked credentials in a privilege-escalation chain that ends in full account takeover."
|
|
4622
|
+
},
|
|
4623
|
+
"framework_coverage": {
|
|
4624
|
+
"NIST-800-53-AC-3": {
|
|
4625
|
+
"covered": true,
|
|
4626
|
+
"adequate": false,
|
|
4627
|
+
"gap": "Access enforcement does not constrain which records/fields a user can read through the API."
|
|
4628
|
+
},
|
|
4629
|
+
"NIST-800-53-SC-28": {
|
|
4630
|
+
"covered": true,
|
|
4631
|
+
"adequate": false,
|
|
4632
|
+
"gap": "Sensitive fields (password hashes, tokens) are readable through the API and directly usable once leaked."
|
|
4633
|
+
},
|
|
4634
|
+
"ALL-AI-PIPELINE-INTEGRITY": {
|
|
4635
|
+
"covered": false,
|
|
4636
|
+
"adequate": false,
|
|
4637
|
+
"gap": "No framework treats an ML data-platform API's object-level authorization and sensitive-field exposure as integrity controls whose failure yields account takeover."
|
|
4638
|
+
}
|
|
4639
|
+
},
|
|
4640
|
+
"compliance_exposure_score": {
|
|
4641
|
+
"percent_audit_passing_orgs_still_exposed": 80,
|
|
4642
|
+
"basis": "ML data-labeling platforms expose rich APIs over collaborative datasets; object-level authorization and serializer field allowlisting are frequently missing, and audits rarely test cross-account field reads.",
|
|
4643
|
+
"theater_pattern": "ai_app_broken_object_authorization"
|
|
4644
|
+
},
|
|
4645
|
+
"ai_discovered_zeroday": false,
|
|
4646
|
+
"ai_discovery_source": "human_researcher",
|
|
4647
|
+
"ai_assist_factor": "none",
|
|
4648
|
+
"new_control_requirements": [
|
|
4649
|
+
{
|
|
4650
|
+
"id": "NEW-CTRL-106",
|
|
4651
|
+
"name": "AI-APP-API-OBJECT-AUTHORIZATION-AND-FIELD-EXPOSURE",
|
|
4652
|
+
"description": "An AI data-platform API (data-labeling, annotation, dataset/registry services) must enforce object-level authorization on every read and must never expose sensitive fields - secrets, session-signing keys, auth tokens, password hashes - through API responses, serializers, or user-controlled query/filter expressions. Use serializer field allowlists (never blanket model serialization), reject ORM/filter inputs that reference fields the caller is not authorized to read, scope every query to the caller's own objects, and store credentials so a read leak is not directly replayable (and rotate exposed secrets). The distinguishing test: as a low-privilege user, craft a filter/query that references another account's password hash or token, and confirm the API refuses it - a platform whose filter/serializer leaks sensitive fields lets an attacker chain disclosure into account impersonation and privilege escalation.",
|
|
4653
|
+
"evidence": "https://github.com/advisories/GHSA-6hjj-gq77-j4qw",
|
|
4654
|
+
"gap_closes": [
|
|
4655
|
+
"NIST-800-53-AC-3",
|
|
4656
|
+
"NIST-800-53-SC-28",
|
|
4657
|
+
"ALL-AI-PIPELINE-INTEGRITY"
|
|
4658
|
+
]
|
|
4659
|
+
}
|
|
4660
|
+
],
|
|
4661
|
+
"_auto_imported": false,
|
|
4662
|
+
"_intake_method": "manual-verified-curation"
|
|
4663
|
+
},
|
|
4664
|
+
"CVE-2023-43791": {
|
|
4665
|
+
"name": "Label Studio Account Impersonation and Privilege Escalation",
|
|
4666
|
+
"lesson_date": "2026-05-25",
|
|
4667
|
+
"attack_vector": {
|
|
4668
|
+
"description": "Label Studio exposes information that, chained with the ORM sensitive-field leak (CVE-2023-47117), lets an attacker impersonate any account and escalate from a low-privilege user to a Django super administrator.",
|
|
4669
|
+
"privileges_required": "low (a low-privilege account; the chain reaches Django superadmin)",
|
|
4670
|
+
"complexity": "low",
|
|
4671
|
+
"ai_factor": "The abused surface is Label Studio, a data-labeling / annotation platform central to ML data pipelines. The lesson: an ML data-platform API must enforce object-level authorization and never expose sensitive fields - this CVE replays the leaked credentials to impersonate and escalate in a privilege-escalation chain that ends in full account takeover."
|
|
4672
|
+
},
|
|
4673
|
+
"framework_coverage": {
|
|
4674
|
+
"NIST-800-53-AC-3": {
|
|
4675
|
+
"covered": true,
|
|
4676
|
+
"adequate": false,
|
|
4677
|
+
"gap": "Access enforcement does not constrain which records/fields a user can read through the API."
|
|
4678
|
+
},
|
|
4679
|
+
"NIST-800-53-SC-28": {
|
|
4680
|
+
"covered": true,
|
|
4681
|
+
"adequate": false,
|
|
4682
|
+
"gap": "Sensitive fields (password hashes, tokens) are readable through the API and directly usable once leaked."
|
|
4683
|
+
},
|
|
4684
|
+
"ALL-AI-PIPELINE-INTEGRITY": {
|
|
4685
|
+
"covered": false,
|
|
4686
|
+
"adequate": false,
|
|
4687
|
+
"gap": "No framework treats an ML data-platform API's object-level authorization and sensitive-field exposure as integrity controls whose failure yields account takeover."
|
|
4688
|
+
}
|
|
4689
|
+
},
|
|
4690
|
+
"compliance_exposure_score": {
|
|
4691
|
+
"percent_audit_passing_orgs_still_exposed": 82,
|
|
4692
|
+
"basis": "ML data-labeling platforms expose rich APIs over collaborative datasets; object-level authorization and serializer field allowlisting are frequently missing, and audits rarely test cross-account field reads.",
|
|
4693
|
+
"theater_pattern": "ai_app_broken_object_authorization"
|
|
4694
|
+
},
|
|
4695
|
+
"ai_discovered_zeroday": false,
|
|
4696
|
+
"ai_discovery_source": "human_researcher",
|
|
4697
|
+
"ai_assist_factor": "none",
|
|
4698
|
+
"new_control_requirements": [
|
|
4699
|
+
{
|
|
4700
|
+
"id": "NEW-CTRL-106",
|
|
4701
|
+
"name": "AI-APP-API-OBJECT-AUTHORIZATION-AND-FIELD-EXPOSURE",
|
|
4702
|
+
"description": "An AI data-platform API (data-labeling, annotation, dataset/registry services) must enforce object-level authorization on every read and must never expose sensitive fields - secrets, session-signing keys, auth tokens, password hashes - through API responses, serializers, or user-controlled query/filter expressions. Use serializer field allowlists (never blanket model serialization), reject ORM/filter inputs that reference fields the caller is not authorized to read, scope every query to the caller's own objects, and store credentials so a read leak is not directly replayable (and rotate exposed secrets). The distinguishing test: as a low-privilege user, craft a filter/query that references another account's password hash or token, and confirm the API refuses it - a platform whose filter/serializer leaks sensitive fields lets an attacker chain disclosure into account impersonation and privilege escalation.",
|
|
4703
|
+
"evidence": "https://github.com/advisories/GHSA-f475-x83m-rx5m",
|
|
4704
|
+
"gap_closes": [
|
|
4705
|
+
"NIST-800-53-AC-3",
|
|
4706
|
+
"NIST-800-53-SC-28",
|
|
4707
|
+
"ALL-AI-PIPELINE-INTEGRITY"
|
|
4708
|
+
]
|
|
4709
|
+
}
|
|
4710
|
+
],
|
|
4711
|
+
"_auto_imported": false,
|
|
4712
|
+
"_intake_method": "manual-verified-curation"
|
|
4713
|
+
},
|
|
4614
4714
|
"CVE-2022-36551": {
|
|
4615
4715
|
"name": "Label Studio Data Import Server-Side Request Forgery",
|
|
4616
4716
|
"lesson_date": "2026-05-25",
|