Lfprojects
Products by Lfprojects Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2024 there have been 1 vulnerability in Lfprojects with an average score of 2.8 out of ten. Last year Lfprojects had 23 security vulnerabilities published. Right now, Lfprojects is on track to have less security vulnerabilities in 2024 than it did last year. Last year, the average CVE base score was greater by 5.15
Year | Vulnerabilities | Average Score |
---|---|---|
2024 | 1 | 2.80 |
2023 | 23 | 7.95 |
2022 | 1 | 7.50 |
2021 | 0 | 0.00 |
2020 | 0 | 0.00 |
2019 | 0 | 0.00 |
2018 | 0 | 0.00 |
It may take a day or so for new Lfprojects vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Lfprojects Security Vulnerabilities
cdo-local-uuid project provides a specialized UUID-generating function
CVE-2024-22194
2.8 - Low
- January 11, 2024
cdo-local-uuid project provides a specialized UUID-generating function that can, on user request, cause a program to generate deterministic UUIDs. An information leakage vulnerability is present in `cdo-local-uuid` at version `0.4.0`, and in `case-utils` in unpatched versions (matching the pattern `0.x.0`) at and since `0.5.0`, before `0.15.0`. The vulnerability stems from a Python function, `cdo_local_uuid.local_uuid()`, and its original implementation `case_utils.local_uuid()`.
Insertion of Sensitive Information Into Debugging Code
A malicious user could use this issue to access internal HTTP(s) servers and in the worst case (ie: aws instance) it could be abuse to get a remote code execution on the victim machine.
CVE-2023-6974
9.8 - Critical
- December 20, 2023
A malicious user could use this issue to access internal HTTP(s) servers and in the worst case (ie: aws instance) it could be abuse to get a remote code execution on the victim machine.
XSPA
A malicious user could use this issue to get command execution on the vulnerable machine and get access to data & models information.
CVE-2023-6975
9.8 - Critical
- December 20, 2023
A malicious user could use this issue to get command execution on the vulnerable machine and get access to data & models information.
Path Traversal: '\..\filename'
This vulnerability is capable of writing arbitrary files into arbitrary locations on the remote filesystem in the context of the server process.
CVE-2023-6976
8.8 - High
- December 20, 2023
This vulnerability is capable of writing arbitrary files into arbitrary locations on the remote filesystem in the context of the server process.
Unrestricted File Upload
This vulnerability enables malicious users to read sensitive files on the server.
CVE-2023-6977
7.5 - High
- December 20, 2023
This vulnerability enables malicious users to read sensitive files on the server.
Path Traversal: '\..\filename'
with only one user interaction(download a malicious config), attackers
CVE-2023-6940
8.8 - High
- December 19, 2023
with only one user interaction(download a malicious config), attackers can gain full command execution on the victim system.
Command Injection
Path Traversal: '\..\filename' in GitHub repository mlflow/m
CVE-2023-6909
7.5 - High
- December 18, 2023
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.
Path Traversal: '\..\filename'
Path Traversal: '\..\filename' in GitHub repository mlflow/m
CVE-2023-6831
8.1 - High
- December 15, 2023
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.
Directory traversal
Improper Neutralization of Special Elements Used in a Template Engine in GitHub repository mlflow/mlflow prior to 2.9.2.
CVE-2023-6709
8.8 - High
- December 12, 2023
Improper Neutralization of Special Elements Used in a Template Engine in GitHub repository mlflow/mlflow prior to 2.9.2.
1336
A reflected Cross-Site Scripting (XSS) vulnerability exists in the mlflow/mlflow repository
CVE-2023-6568
6.1 - Medium
- December 07, 2023
A reflected Cross-Site Scripting (XSS) vulnerability exists in the mlflow/mlflow repository, specifically within the handling of the Content-Type header in POST requests. An attacker can inject malicious JavaScript code into the Content-Type header, which is then improperly reflected back to the user without adequate sanitization or escaping, leading to arbitrary JavaScript execution in the context of the victim's browser. The vulnerability is present in the mlflow/server/auth/__init__.py file, where the user-supplied Content-Type header is directly injected into a Python formatted string and returned to the user, facilitating the XSS attack.
XSS
An issue in MLFlow versions 2.8.1 and before
CVE-2023-43472
7.5 - High
- December 05, 2023
An issue in MLFlow versions 2.8.1 and before allows a remote attacker to obtain sensitive information via a crafted request to REST API.
An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirment.
CVE-2023-6014
9.8 - Critical
- November 16, 2023
An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirment.
An attacker can overwrite any file on the server hosting MLflow without any authentication.
CVE-2023-6018
9.8 - Critical
- November 16, 2023
An attacker can overwrite any file on the server hosting MLflow without any authentication.
MLflow allowed arbitrary files to be PUT onto the server.
CVE-2023-6015
7.5 - High
- November 16, 2023
MLflow allowed arbitrary files to be PUT onto the server.
OS Command Injection in GitHub repository mlflow/mlflow prior to 2.6.0.
CVE-2023-4033
7.8 - High
- August 01, 2023
OS Command Injection in GitHub repository mlflow/mlflow prior to 2.6.0.
Shell injection
Apptainer is an open source container platform
CVE-2023-38496
3.3 - Low
- July 25, 2023
Apptainer is an open source container platform. Version 1.2.0-rc.2 introduced an ineffective privilege drop when requesting container network setup, therefore subsequent functions are called with root privileges, the attack surface is rather limited for users but an attacker could possibly craft a starter config to delete any directory on the host filesystems. A security fix has been included in Apptainer 1.2.1. There is no known workaround outside of upgrading to Apptainer 1.2.1.
Path Traversal: '\..\filename' in GitHub repository mlflow/m
CVE-2023-2780
9.8 - Critical
- May 17, 2023
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.3.1.
Path Traversal: '\..\filename'
A directory traversal vulnerability in the /get-artifact API method of the mlflow platform up to v2.0.1
CVE-2023-30172
7.5 - High
- May 11, 2023
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.
Directory traversal
Relative Path Traversal in GitHub repository mlflow/mlflow prior to 2.3.1.
CVE-2023-2356
7.5 - High
- April 28, 2023
Relative Path Traversal in GitHub repository mlflow/mlflow prior to 2.3.1.
Relative Path Traversal
Apptainer is an open source container platform for Linux
CVE-2023-30549
7.8 - High
- April 25, 2023
Apptainer is an open source container platform for Linux. There is an ext4 use-after-free flaw that is exploitable through versions of Apptainer < 1.1.0 and installations that include apptainer-suid < 1.1.8 on older operating systems where that CVE has not been patched. That includes Red Hat Enterprise Linux 7, Debian 10 buster (unless the linux-5.10 package is installed), Ubuntu 18.04 bionic and Ubuntu 20.04 focal. Use-after-free flaws in the kernel can be used to attack the kernel for denial of service and potentially for privilege escalation. Apptainer 1.1.8 includes a patch that by default disables mounting of extfs filesystem types in setuid-root mode, while continuing to allow mounting of extfs filesystems in non-setuid "rootless" mode using fuse2fs. Some workarounds are possible. Either do not install apptainer-suid (for versions 1.1.0 through 1.1.7) or set `allow setuid = no` in apptainer.conf. This requires having unprivileged user namespaces enabled and except for apptainer 1.1.x versions will disallow mounting of sif files, extfs files, and squashfs files in addition to other, less significant impacts. (Encrypted sif files are also not supported unprivileged in apptainer 1.1.x.). Alternatively, use the `limit containers` options in apptainer.conf/singularity.conf to limit sif files to trusted users, groups, and/or paths, and set `allow container extfs = no` to disallow mounting of extfs overlay files. The latter option by itself does not disallow mounting of extfs overlay partitions inside SIF files, so that's why the former options are also needed.
Dangling pointer
FP.io VPP (Vector Packet Processor) 22.10
CVE-2022-46397
7.5 - High
- March 28, 2023
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.
Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.2.2.
CVE-2023-1176
3.3 - Low
- March 24, 2023
Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.2.2.
Absolute Path Traversal
Path Traversal: '\..\filename' in GitHub repository mlflow/m
CVE-2023-1177
9.8 - Critical
- March 24, 2023
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.2.1.
Path Traversal: '\..\filename'
Modelina is a library for generating data models based on inputs such as AsyncAPI, OpenAPI, or JSON Schema documents
CVE-2023-23619
8.8 - High
- January 26, 2023
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."
Code Injection