Insecure Temporary File in GitHub repository mlflow/mlflow prior to 1.23.1.
Published 2022-02-23 09:15:14
Updated 2023-06-27 18:13:22
Source huntr.dev
View at NVD,   CVE.org

Products affected by CVE-2022-0736

Exploit prediction scoring system (EPSS) score for CVE-2022-0736

0.12%
Probability of exploitation activity in the next 30 days EPSS Score History
~ 47 %
Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2022-0736

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
5.0
MEDIUM AV:N/AC:L/Au:N/C:N/I:N/A:P
10.0
2.9
NIST
8.2
HIGH CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
3.9
4.2
huntr.dev
7.5
HIGH CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
3.9
3.6
NIST

CWE ids for CVE-2022-0736

  • Creating and using insecure temporary files can leave application and system data vulnerable to attack.
    Assigned by: security@huntr.dev (Secondary)
  • The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
    Assigned by: nvd@nist.gov (Primary)

References for CVE-2022-0736

Jump to
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!