CVE-2024-2032

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 v3 3.1 LOW

3.1^/10

CVSS v3 : LOW

Vector : AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:L

Exploitability : 0.5 / Impact : 2.5

Attack Vector NETWORK

Attack Complexity HIGH

Privileges Required HIGH

User Interaction REQUIRED

Confidentiality Impact NONE

Integrity Impact LOW

Availability Impact LOW

Scope UNCHANGED

References

Link	Resource
https://github.com/zenml-io/zenml/commit/afcaf741ef9114c9b32f722f101b97de3d8d147b
https://huntr.com/bounties/6199cd5d-611f-4ea9-96c5-52a952ba5a56

Configurations

No configuration.

History

No history.

Information

Published : 2024-06-06 19:15

Updated : 2024-06-07 14:56

NVD link : CVE-2024-2032

Mitre link : CVE-2024-2032

CVE.ORG link : CVE-2024-2032

JSON object : View

Products Affected

No product.

CWE

CWE-366

Race Condition within a Thread

{"id": "CVE-2024-2032", "cveTags": [], "metrics": {"cvssMetricV30": [{"type": "Secondary", "source": "security@huntr.dev", "cvssData": {"scope": "UNCHANGED", "version": "3.0", "baseScore": 3.1, "attackVector": "NETWORK", "baseSeverity": "LOW", "vectorString": "CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "REQUIRED", "attackComplexity": "HIGH", "availabilityImpact": "LOW", "privilegesRequired": "HIGH", "confidentialityImpact": "NONE"}, "impactScore": 2.5, "exploitabilityScore": 0.5}]}, "published": "2024-06-06T19:15:53.060", "references": [{"url": "https://github.com/zenml-io/zenml/commit/afcaf741ef9114c9b32f722f101b97de3d8d147b", "source": "security@huntr.dev"}, {"url": "https://huntr.com/bounties/6199cd5d-611f-4ea9-96c5-52a952ba5a56", "source": "security@huntr.dev"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security@huntr.dev", "description": [{"lang": "en", "value": "CWE-366"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Existe una vulnerabilidad de condici\u00f3n de ejecuci\u00f3n en las versiones de zenml-io/zenml hasta la 0.55.3 incluida, que permite la creaci\u00f3n de m\u00faltiples usuarios con el mismo nombre de usuario cuando las solicitudes se env\u00edan en paralelo. Este problema se solucion\u00f3 en la versi\u00f3n 0.55.5. La vulnerabilidad surge debido al manejo insuficiente de solicitudes simult\u00e1neas de creaci\u00f3n de usuarios, lo que genera inconsistencias en los datos y posibles problemas de autenticaci\u00f3n. Espec\u00edficamente, los procesos simult\u00e1neos pueden sobrescribir o da\u00f1ar los datos del usuario, complicando la identificaci\u00f3n del usuario y planteando riesgos de seguridad. Este problema es particularmente preocupante para las API que dependen de nombres de usuario como par\u00e1metros de entrada, como PUT /api/v1/users/test_race, donde podr\u00eda generar m\u00e1s complicaciones."}], "lastModified": "2024-06-07T14:56:05.647", "sourceIdentifier": "security@huntr.dev"}