Race Condition Vulnerability in zenml-io/zenml
A race condition vulnerability exists in zenml-io/zenml versions up to and including 0.55.3, which allows for the creation of multiple users with the same username when requests are sent in parallel. This issue was fixed in version 0.55.5. The vulnerability arises due to insufficient handling of concurrent user creation requests, leading to data inconsistencies and potential authentication problems. Specifically, concurrent processes may overwrite or corrupt user data, complicating user identification and posing security risks. This issue is particularly concerning for APIs that rely on usernames as input parameters, such as PUT /api/v1/users/test_race, where it could lead to further complications.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2024-2032
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 01:03 UTC · Revision 1
Source evidence
Race Condition Vulnerability in zenml-io/zenml
core-osv · Original sourcePublished 6 Jun 2024, 18:49 UTC
A race condition vulnerability exists in zenml-io/zenml versions up to and including 0.55.3, which allows for the creation of multiple users with the same username when requests are sent in parallel. This issue was fixed in version 0.55.5. The vulnerability arises due to insufficient handling of concurrent user creation requests, leading to data inconsistencies and potential authentication problems. Specifically, concurrent processes may overwrite or corrupt user data, complicating user identification and posing security risks. This issue is particularly concerning for APIs that rely on usernames as input parameters, such as PUT /api/v1/users/test_race, where it could lead to further complications.
osv:CVE-2024-2032
Complete source record
{
"id": "f665a90f71192e8a4f832eb8f533423aeed9f04d6393568d43cd0bf26726f473",
"url": "https://osv.dev/vulnerability/CVE-2024-2032",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Race Condition Vulnerability in zenml-io/zenml",
"summary": "A race condition vulnerability exists in zenml-io/zenml versions up to and including 0.55.3, which allows for the creation of multiple users with the same username when requests are sent in parallel. This issue was fixed in version 0.55.5. The vulnerability arises due to insufficient handling of concurrent user creation requests, leading to data inconsistencies and potential authentication problems. Specifically, concurrent processes may overwrite or corrupt user data, complicating user identification and posing security risks. This issue is particularly concerning for APIs that rely on usernames as input parameters, such as PUT /api/v1/users/test_race, where it could lead to further complications.",
"evidence": "osv:CVE-2024-2032",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2024-2032",
"aliases": [
"CVE-2024-2032",
"GHSA-c546-8jmq-hprj",
"PYSEC-2024-105"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:L"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/zenml-io/zenml",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "8e13b42c1d502ed66ee3fc39e0e293e8bfeaffdb"
},
{
"fixed": "afcaf741ef9114c9b32f722f101b97de3d8d147b"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:zenml:zenml:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "0.55.5"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "afcaf741ef9114c9b32f722f101b97de3d8d147b"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"0.55.4",
"0.54.1",
"0.54.0",
"0.47.0",
"0.46.1",
"0.45.6",
"0.45.5",
"0.45.4",
"0.45.3",
"0.45.2",
"0.45.1",
"0.44.3",
"0.45.0",
"0.13.1",
"0.21.1",
"0.32.1",
"0.35.0",
"0.39.1",
"0.44.2",
"0.42.0",
"0.41.0",
"0.44.1",
"0.44.0",
"0.43.0",
"0.39.0",
"0.40.0",
"0.40.2",
"0.40.1",
"0.38.0",
"0.37.0",
"0.36.1",
"0.35.1",
"0.34.0",
"0.33.0",
"0.32.0",
"0.31.1",
"0.31.0",
"0.30.0",
"0.23.0",
"0.22.0",
"0.21.0",
"0.20.5",
"0.20.3",
"0.13.2",
"0.13.0",
"0.12.0",
"0.11.0",
"0.10.0",
"0.9.0",
"0.8.1",
"0.8.1rc0",
"0.7.1",
"0.7.0",
"0.6.3",
"0.6.2",
"0.5.7",
"0.5.6",
"0.5.5",
"0.5.4",
"0.5.3",
"0.5.2",
"0.5.1",
"0.5.0",
"0.5.0rc2",
"0.5.0rc1",
"0.3.9rc2",
"0.3.9rc1",
"0.3.8",
"0.3.7.1rc5",
"0.3.7.1rc4",
"0.3.7.1rc3",
"0.3.7.1rc2",
"0.3.7.1rc1",
"0.3.7.1rc0",
"0.3.7",
"0.3.7rc0",
"0.3.6.1",
"0.3.6",
"0.3.6rc0",
"0.3.5",
"0.3.5rc0",
"0.3.4",
"0.3.4rc0",
"0.3.3",
"0.3.3rc0",
"0.3.2",
"0.3.1",
"0.3.1rc0",
"0.3.0",
"0.2.0",
"0.2.0rc2",
"0.2.0rc1",
"0.1.3",
"0.1.3rc0",
"0.1.2",
"0.1.1",
"0.1.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-2032.json"
}
}
],
"modified": "2026-10-28T02:30:41.430455003Z",
"provider": "osv",
"references": [
"https://huntr.com/bounties/6199cd5d-611f-4ea9-96c5-52a952ba5a56",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/2xxx/CVE-2024-2032.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-2032",
"https://github.com/zenml-io/zenml/commit/afcaf741ef9114c9b32f722f101b97de3d8d147b"
],
"provider_metadata": {
"cwe_ids": [
"CWE-366"
],
"cna_assigner": "@huntr_ai",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/2xxx/CVE-2024-2032.json"
}
},
"related_cves": [
{
"value": "CVE-2024-2032",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 508888,
"published_at": "2024-06-06T18:49:18.482+00:00"
}