ghsa-qpgc-w4mg-6v92
Vulnerability from github
Published
2024-11-25 18:33
Modified
2024-11-25 19:41
Severity ?
7.0 (High) - CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
7.3 (High) - CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
7.3 (High) - CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Summary
MLflow's excessive directory permissions allow local privilege escalation
Details
Excessive directory permissions in MLflow leads to local privilege escalation when using spark_udf. 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 spark_udf() MLflow API is called.
{ affected: [ { package: { ecosystem: "PyPI", name: "mlflow", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "2.16.0", }, ], type: "ECOSYSTEM", }, ], }, ], aliases: [ "CVE-2024-27134", ], database_specific: { cwe_ids: [ "CWE-276", ], github_reviewed: true, github_reviewed_at: "2024-11-25T19:41:56Z", nvd_published_at: "2024-11-25T14:15:06Z", severity: "HIGH", }, details: "Excessive directory permissions in MLflow leads to local privilege escalation when using spark_udf. 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 spark_udf() MLflow API is called.", id: "GHSA-qpgc-w4mg-6v92", modified: "2024-11-25T19:41:56Z", published: "2024-11-25T18:33:26Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2024-27134", }, { type: "WEB", url: "https://github.com/mlflow/mlflow/pull/10874", }, { type: "WEB", url: "https://github.com/mlflow/mlflow/commit/0b1d995d66a678153e01ed3040f3f4dfc16a0d6b", }, { type: "PACKAGE", url: "https://github.com/mlflow/mlflow", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H", type: "CVSS_V3", }, { score: "CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N", type: "CVSS_V4", }, ], summary: "MLflow's excessive directory permissions allow local privilege escalation", }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.