An attacker can pass a malicious malformed token which causes unexpected memory to be consumed during parsing.
The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Gatekeeper 3.15 for RHEL 9 | RedHat | gatekeeper/gatekeeper-operator-bundle:v3.15.4-1 | * |
Gatekeeper 3.15 for RHEL 9 | RedHat | gatekeeper/gatekeeper-rhel9:v3.15.1-30 | * |
Gatekeeper 3.15 for RHEL 9 | RedHat | gatekeeper/gatekeeper-rhel9-operator:v3.15.4-1 | * |
Gatekeeper 3.17 for RHEL 9 | RedHat | gatekeeper/gatekeeper-operator-bundle:v3.17.2-2 | * |
Gatekeeper 3.17 for RHEL 9 | RedHat | gatekeeper/gatekeeper-rhel9:v3.17.2-5 | * |
Gatekeeper 3.17 for RHEL 9 | RedHat | gatekeeper/gatekeeper-rhel9-operator:v3.17.2-4 | * |
Red Hat Advanced Cluster Management for Kubernetes 2.13 for RHEL 9 | RedHat | rhacm2/volsync-operator-bundle:v0.12.1-2 | * |
Red Hat Advanced Cluster Management for Kubernetes 2.13 for RHEL 9 | RedHat | rhacm2/volsync-rhel9:v0.12.1-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-central-db-rhel8:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-collector-rhel8:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-collector-slim-rhel8:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-main-rhel8:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-operator-bundle:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-rhel8-operator:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-roxctl-rhel8:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-scanner-db-rhel8:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-scanner-db-slim-rhel8:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-scanner-rhel8:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-scanner-slim-rhel8:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-scanner-v4-db-rhel8:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.5 | RedHat | advanced-cluster-security/rhacs-scanner-v4-rhel8:4.5.7-2 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-central-db-rhel8:4.6.3-2 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-collector-rhel8:4.6.3-2 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-collector-slim-rhel8:4.6.3-2 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-main-rhel8:4.6.3-2 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-operator-bundle:4.6.3-3 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-rhel8-operator:4.6.3-2 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-roxctl-rhel8:4.6.3-2 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-scanner-db-rhel8:4.6.3-2 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-scanner-rhel8:4.6.3-2 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-scanner-slim-rhel8:4.6.3-2 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-scanner-v4-db-rhel8:4.6.3-2 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | advanced-cluster-security/rhacs-scanner-v4-rhel8:4.6.3-3 | * |
Red Hat Advanced Cluster Security 4.6 | RedHat | rhacs-scanner-db-slim-container-4.6.3-2 | * |
Red Hat Enterprise Linux 9 | RedHat | opentelemetry-collector-0:0.107.0-8.el9_5 | * |
Often, complex inputs are expected to follow a particular syntax, which is either assumed by the input itself, or declared within metadata such as headers. The syntax could be for data exchange formats, markup languages, or even programming languages. When untrusted input is not properly validated for the expected syntax, attackers could cause parsing failures, trigger unexpected errors, or expose latent vulnerabilities that might not be directly exploitable if the input had conformed to the syntax.