CVE-2024-2032
lowpriority · track · 12EPSS 0.003 · 22 %ileEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- GHSA-c546-8jmq-hprjRace condition in zenml2024-06-06ghsa · osvUS
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.
- PYSEC-2024-1052024-06-06vendor · osvUS
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.
also known as (6)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (8)
External citations — patches, advisories, analysis.
- https://cxsecurity.com/cveshow/CVE-2024-2032/cnnvd
- https://github.com/zenml-io/zenml/commit/afcaf741ef9114c9b32f722f101b97de3d8d147bcnnvd
- https://github.com/zenml-io/zenml/releases/tag/0.58.1Patchcnnvd
- https://huntr.com/bounties/6199cd5d-611f-4ea9-96c5-52a952ba5a56cnnvd
- https://github.com/zenml-io/zenml/commit/afcaf741ef9114c9b32f722f101b97de3d8d147benisa_euvd
- https://huntr.com/bounties/6199cd5d-611f-4ea9-96c5-52a952ba5a56enisa_euvd
- https://github.com/zenml-io/zenml/commit/afcaf741ef9114c9b32f722f101b97de3d8d147bPatchnvd
- https://huntr.com/bounties/6199cd5d-611f-4ea9-96c5-52a952ba5a56Third Party Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan