Filtered by vendor Lfprojects
Subscribe
Total
27 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2022-0736 | 1 Lfprojects | 1 Mlflow | 2023-06-27 | 5.0 MEDIUM | 7.5 HIGH |
| Insecure Temporary File in GitHub repository mlflow/mlflow prior to 1.23.1. | |||||
| CVE-2023-2780 | 1 Lfprojects | 1 Mlflow | 2023-05-25 | N/A | 9.8 CRITICAL |
| Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.3.1. | |||||
| CVE-2023-30172 | 1 Lfprojects | 1 Mlflow | 2023-05-22 | N/A | 7.5 HIGH |
| A directory traversal vulnerability in the /get-artifact API method of the mlflow platform up to v2.0.1 allows attackers to read arbitrary files on the server via the path parameter. | |||||
| CVE-2023-2356 | 1 Lfprojects | 1 Mlflow | 2023-05-05 | N/A | 7.5 HIGH |
| Relative Path Traversal in GitHub repository mlflow/mlflow prior to 2.3.1. | |||||
| CVE-2022-46397 | 1 Lfprojects | 1 Vector Packet Processor | 2023-04-06 | N/A | 7.5 HIGH |
| FP.io VPP (Vector Packet Processor) 22.10, 22.06, 22.02, 21.10, 21.06, 21.01, 20.09, 20.05, 20.01, 19.08, and 19.04 Generates a Predictable IV with CBC Mode. | |||||
| CVE-2023-1176 | 1 Lfprojects | 1 Mlflow | 2023-03-28 | N/A | 3.3 LOW |
| Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.2.2. | |||||
| CVE-2023-23619 | 1 Lfprojects | 1 Modelina | 2023-02-06 | N/A | 8.8 HIGH |
| Modelina is a library for generating data models based on inputs such as AsyncAPI, OpenAPI, or JSON Schema documents. Versions prior to 1.0.0 are vulnerable to Code injection. This issue affects anyone who is using the default presets and/or does not handle the functionality themself. This issue has been partially mitigated in version 1.0.0, with the maintainer's GitHub Security Advisory (GHSA) noting "It is impossible to fully guard against this, because users have access to the original raw information. However, as of version 1, if you only access the constrained models, you will not encounter this issue. Further similar situations are NOT seen as a security issue, but intended behavior." The suggested workaround from the maintainers is "Fully custom presets that change the entire rendering process which can then escape the user input." | |||||