CVE-2024-27134: Excessive directory permissions in MLflow leads to local privilege escalation when using spark_udf

Published Nov 25, 2024
·
Updated

Excessive directory permissions in MLflow leads to local privilege escalation when using sparkudf. This behavior can be exploited by a local attacker to gain elevated permissions by using a ToCToU attack. The issue is only relevant when the sparkudf() MLflow API is called.

Affected Software

2 affected componentsFixes available
pip/mlflow<2.16.0
2.16.0
Lfprojects Mlflow<2.16.0

Event History

Nov 25, 2024
CVE Published
via MITRE·01:48 PM
Data Sourced
via MITRE·01:48 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·06:33 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-27134?

CVE-2024-27134 has a severity rating indicating a vulnerability that can lead to local privilege escalation.

2

How do I fix CVE-2024-27134?

To fix CVE-2024-27134, update MLflow to version 2.16.0 or later.

3

What software is affected by CVE-2024-27134?

CVE-2024-27134 affects MLflow versions prior to 2.16.0.

4

What is a ToCToU attack in relation to CVE-2024-27134?

A ToCToU attack in CVE-2024-27134 refers to a Time-of-Check Time-of-Use vulnerability that can be exploited by attackers with local access.

5

When does CVE-2024-27134 become relevant?

CVE-2024-27134 is relevant specifically when the spark_udf() API is used in MLflow.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203