CVE-2024-56512 |
Description: Apache NiFi 1.10.0 through 2.0.0 are missing fine-grained authorization checking for Parameter Contexts, referenced Controller Services, and referenced Parameter Providers, when creating new Process Groups.
Creating a new Process Group can include binding to a Parameter Context, but in cases where the Process Group did not reference any Parameter values, the framework did not check user authorization for the bound Parameter Context. Missing authorization for a bound Parameter Context enabled clients to download non-sensitive Parameter values after creating the Process Group.
Creating a new Process Group can also include referencing existing Controller Services or Parameter Providers. The framework did not check user authorization for referenced Controller Services or Parameter Providers, enabling clients to create Process Groups and use these components that were otherwise unauthorized.
This vulnerability is limited in scope to authenticated users authorized to create Process Groups. The scope is further limited to deployments with component-based authorization policies. Upgrading to Apache NiFi 2.1.0 is the recommended mitigation, which includes authorization checking for Parameter and Controller Service references on Process Group creation.
References
https://nvd.nist.gov/vuln/detail/CVE-2024-56512
https://lists.apache.org/thread/cjc8fns5kjsho0s7vonlnojokyfx47wn
http://www.openwall.com/lists/oss-security/2024/12/28/1
https://github.com/apache/nifi/commit/f744deebf9a9eff...
CVSS: LOW (2.1) EPSS Score: 0.05%
December 30th, 2024 (6 months ago)
|
CVE-2024-56512 |
Description: Apache NiFi 1.10.0 through 2.0.0 are missing fine-grained authorization checking for Parameter Contexts, referenced Controller Services, and referenced Parameter Providers, when creating new Process Groups.
Creating a new Process Group can include binding to a Parameter Context, but in cases where the Process Group did not reference any Parameter values, the framework did not check user authorization for the bound Parameter Context. Missing authorization for a bound Parameter Context enabled clients to download non-sensitive Parameter values after creating the Process Group.
Creating a new Process Group can also include referencing existing Controller Services or Parameter Providers. The framework did not check user authorization for referenced Controller Services or Parameter Providers, enabling clients to create Process Groups and use these components that were otherwise unauthorized.
This vulnerability is limited in scope to authenticated users authorized to create Process Groups. The scope is further limited to deployments with component-based authorization policies. Upgrading to Apache NiFi 2.1.0 is the recommended mitigation, which includes authorization checking for Parameter and Controller Service references on Process Group creation.
References
https://nvd.nist.gov/vuln/detail/CVE-2024-56512
https://lists.apache.org/thread/cjc8fns5kjsho0s7vonlnojokyfx47wn
http://www.openwall.com/lists/oss-security/2024/12/28/1
https://github.com/apache/nifi/commit/f744deebf9a9eff...
CVSS: LOW (2.1) EPSS Score: 0.05%
December 30th, 2024 (6 months ago)
|
CVE-2024-56512 |
Description: Apache NiFi 1.10.0 through 2.0.0 are missing fine-grained authorization checking for Parameter Contexts, referenced Controller Services, and referenced Parameter Providers, when creating new Process Groups.
Creating a new Process Group can include binding to a Parameter Context, but in cases where the Process Group did not reference any Parameter values, the framework did not check user authorization for the bound Parameter Context. Missing authorization for a bound Parameter Context enabled clients to download non-sensitive Parameter values after creating the Process Group.
Creating a new Process Group can also include referencing existing Controller Services or Parameter Providers. The framework did not check user authorization for referenced Controller Services or Parameter Providers, enabling clients to create Process Groups and use these components that were otherwise unauthorized.
This vulnerability is limited in scope to authenticated users authorized to create Process Groups. The scope is further limited to deployments with component-based authorization policies. Upgrading to Apache NiFi 2.1.0 is the recommended mitigation, which includes authorization checking for Parameter and Controller Service references on Process Group creation.
References
https://nvd.nist.gov/vuln/detail/CVE-2024-56512
https://lists.apache.org/thread/cjc8fns5kjsho0s7vonlnojokyfx47wn
http://www.openwall.com/lists/oss-security/2024/12/28/1
https://github.com/apache/nifi/commit/f744deebf9a9eff...
CVSS: LOW (2.1) EPSS Score: 0.05%
December 30th, 2024 (6 months ago)
|
CVE-2024-56512 |
Description: Apache NiFi 1.10.0 through 2.0.0 are missing fine-grained authorization checking for Parameter Contexts, referenced Controller Services, and referenced Parameter Providers, when creating new Process Groups.
Creating a new Process Group can include binding to a Parameter Context, but in cases where the Process Group did not reference any Parameter values, the framework did not check user authorization for the bound Parameter Context. Missing authorization for a bound Parameter Context enabled clients to download non-sensitive Parameter values after creating the Process Group.
Creating a new Process Group can also include referencing existing Controller Services or Parameter Providers. The framework did not check user authorization for referenced Controller Services or Parameter Providers, enabling clients to create Process Groups and use these components that were otherwise unauthorized.
This vulnerability is limited in scope to authenticated users authorized to create Process Groups. The scope is further limited to deployments with component-based authorization policies. Upgrading to Apache NiFi 2.1.0 is the recommended mitigation, which includes authorization checking for Parameter and Controller Service references on Process Group creation.
CVSS: LOW (2.1) EPSS Score: 0.05%
December 29th, 2024 (6 months ago)
|
CVE-2024-56433 |
Description: shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.
CVSS: LOW (3.6) EPSS Score: 0.05%
December 27th, 2024 (6 months ago)
|
CVE-2024-47157 |
Description: Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service exceptions.
CVSS: LOW (2.9) EPSS Score: 0.04%
December 27th, 2024 (6 months ago)
|
CVE-2024-47156 |
Description: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.
CVSS: LOW (3.3) EPSS Score: 0.04%
December 27th, 2024 (6 months ago)
|
CVE-2024-47150 |
Description: Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak.
CVSS: LOW (3.3) EPSS Score: 0.04%
December 27th, 2024 (6 months ago)
|
CVE-2024-47149 |
Description: Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service exceptions.
CVSS: LOW (3.3) EPSS Score: 0.04%
December 27th, 2024 (6 months ago)
|
CVE-2023-5117 |
Description: An issue was discovered in GitLab CE/EE affecting all versions before 17.6.0 in which users were unaware that files uploaded to comments on confidential issues and epics of public projects could be accessed without authentication via a direct link to the uploaded file URL.
CVSS: LOW (3.7) EPSS Score: 0.04%
December 27th, 2024 (6 months ago)
|