CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 1CVE-2023-29195 – Vitess VTAdmin users that can create shards can deny access to other functions
https://notcve.org/view.php?id=CVE-2023-29195
Vitess is a database clustering system for horizontal scaling of MySQL through generalized sharding. Prior to version 16.0.2, users can either intentionally or inadvertently create a shard containing `/` characters from VTAdmin such that from that point on, anyone who tries to create a new shard from VTAdmin will receive an error. Attempting to view the keyspace(s) will also no longer work. Creating a shard using `vtctldclient` does not have the same problem because the CLI validates the input correctly. Version 16.0.2, corresponding to version 0.16.2 of the `go` module, contains a patch for this issue. • https://github.com/vitessio/vitess/commit/9dcbd7de3180f47e94f54989fb5c66daea00c920 https://github.com/vitessio/vitess/issues/12842 https://github.com/vitessio/vitess/pull/12843 https://github.com/vitessio/vitess/releases/tag/v16.0.2 https://github.com/vitessio/vitess/security/advisories/GHSA-pqj7-jx24-wj7w https://pkg.go.dev/vitess.io/vitess@v0.16.2 • CWE-20: Improper Input Validation CWE-703: Improper Check or Handling of Exceptional Conditions •
CVSS: 7.8EPSS: 0%CPEs: 1EXPL: 0CVE-2023-30840 – On a compromised node, the fluid-csi service account can be used to modify node specs
https://notcve.org/view.php?id=CVE-2023-30840
Fluid is an open source Kubernetes-native distributed dataset orchestrator and accelerator for data-intensive applications. Starting in version 0.7.0 and prior to version 0.8.6, if a malicious user gains control of a Kubernetes node running fluid csi pod (controlled by the `csi-nodeplugin-fluid` node-daemonset), they can leverage the fluid-csi service account to modify specs of all the nodes in the cluster. However, since this service account lacks `list node` permissions, the attacker may need to use other techniques to identify vulnerable nodes. Once the attacker identifies and modifies the node specs, they can manipulate system-level-privileged components to access all secrets in the cluster or execute pods on other nodes. This allows them to elevate privileges beyond the compromised node and potentially gain full privileged access to the whole cluster. To exploit this vulnerability, the attacker can make all other nodes unschedulable (for example, patch node with taints) and wait for system-critical components with high privilege to appear on the compromised node. However, this attack requires two prerequisites: a compromised node and identifying all vulnerable nodes through other means. Version 0.8.6 contains a patch for this issue. • https://github.com/fluid-cloudnative/fluid/commit/77c8110a3d1ec077ae2bce6bd88d296505db1550 https://github.com/fluid-cloudnative/fluid/commit/91c05c32db131997b5ca065e869c9918a125c149 https://github.com/fluid-cloudnative/fluid/releases/tag/v0.8.6 https://github.com/fluid-cloudnative/fluid/security/advisories/GHSA-93xx-cvmc-9w3v • CWE-863: Incorrect Authorization •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2023-30551 – Rekor's compressed archives can result in OOM conditions
https://notcve.org/view.php?id=CVE-2023-30551
Rekor is an open source software supply chain transparency log. Rekor prior to version 1.1.1 may crash due to out of memory (OOM) conditions caused by reading archive metadata files into memory without checking their sizes first. Verification of a JAR file submitted to Rekor can cause an out of memory crash if files within the META-INF directory of the JAR are sufficiently large. Parsing of an APK file submitted to Rekor can cause an out of memory crash if the .SIGN or .PKGINFO files within the APK are sufficiently large. The OOM crash has been patched in Rekor version 1.1.1. • https://github.com/sigstore/rekor/commit/cf42ace82667025fe128f7a50cf6b4cdff51cc48 https://github.com/sigstore/rekor/releases/tag/v1.1.1 https://github.com/sigstore/rekor/security/advisories/GHSA-2h5h-59f5-c5x9 https://access.redhat.com/security/cve/CVE-2023-30551 https://bugzilla.redhat.com/show_bug.cgi?id=2196656 • CWE-770: Allocation of Resources Without Limits or Throttling •
CVSS: 6.0EPSS: 0%CPEs: 1EXPL: 1CVE-2023-30841 – Ironic and ironic-inspector deployed within Baremetal Operator may expose as ConfigMaps
https://notcve.org/view.php?id=CVE-2023-30841
Baremetal Operator (BMO) is a bare metal host provisioning integration for Kubernetes. Prior to version 0.3.0, ironic and ironic-inspector deployed within Baremetal Operator using the included `deploy.sh` store their `.htpasswd` files as ConfigMaps instead of Secrets. This causes the plain-text username and hashed password to be readable by anyone having a cluster-wide read-access to the management cluster, or access to the management cluster's Etcd storage. This issue is patched in baremetal-operator PR#1241, and is included in BMO release 0.3.0 onwards. As a workaround, users may modify the kustomizations and redeploy the BMO, or recreate the required ConfigMaps as Secrets per instructions in baremetal-operator PR#1241. • https://github.com/metal3-io/baremetal-operator/pull/1241 https://github.com/metal3-io/baremetal-operator/security/advisories/GHSA-9wh7-397j-722m https://access.redhat.com/security/cve/CVE-2023-30841 https://bugzilla.redhat.com/show_bug.cgi?id=2190116 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-319: Cleartext Transmission of Sensitive Information •
CVSS: 6.7EPSS: 0%CPEs: 1EXPL: 0CVE-2023-2250
https://notcve.org/view.php?id=CVE-2023-2250
A flaw was found in the Open Cluster Management (OCM) when a user have access to the worker nodes which has the cluster-manager-registration-controller or cluster-manager deployments. A malicious user can take advantage of this and bind the cluster-admin to any service account or using the service account to list all secrets for all kubernetes namespaces, leading into a cluster-level privilege escalation. • https://github.com/open-cluster-management-io/registration-operator/pull/344 • CWE-268: Privilege Chaining •