Vulnerabilities · 2024 · Zenml
CVE-2024-2032
Zenml vulnerability
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 products
Zenml. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Zenml runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/zenml-io/zenml/commit/afcaf741ef9114c9b32f722f101b97de3d8d147b · Patch
- huntr.com/bounties/6199cd5d-611f-4ea9-96c5-52a952ba5a56 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2024-2032
- github.com/pypa/advisory-database/tree/main/vulns/zenml/PYSEC-2024-105.yaml
- github.com/advisories/GHSA-c546-8jmq-hprj
- nvd.nist.gov/vuln/detail/CVE-2024-2032
- cve.org/CVERecord?id=CVE-2024-2032
More vulnerabilities in Zenml products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.