Skip to content
Sign in
CVE-2024-20323.1LowCWE-366

CVE-2024-2032: Race Condition Vulnerability in zenml-io/zenml

zenml-io · zenml-io/zenml

Vendor fix available · Affected: zenml-io/zenml · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.3%probability of exploitation in the next 30 days
21st percentile
050100

Higher than 21% of scored CVEs

3.1LowCVSS 3.0
Low

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • zenml-io · zenml-io/zenmlbefore 0.55.5

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
zenml-io
Published
June 2024

CoverageNo articles yet

No CyberSIXT article names CVE-2024-2032 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in