← Übersicht Red Hat Enterprise Linux

Memory Exhaustion in Expr Parser with Unrestricted Input

CVE-2025-29786 · AZL-58848 · AZL-58857 · AZL-58861 · AZL-58872 · DEBIAN-CVE-2025-29786 · GHSA-93mq-9ffx-83m2 · GO-2025-3525 · UBUNTU-CVE-2025-29786 · openSUSE-SU-2025:15006-1

Hoch · CVSS 7.5 SUSE: importantSUSE: moderateUbuntu: mediumRed Hat: Important Netzwerk · ohne Login Fix verfügbar

Veröffentlicht
17.03.2025 14:15
Zuletzt geändert
19.11.2026
EPSS (30 Tage)
0.6 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Beschreibung

Originaltext der Quelle, nicht übersetzt.

Expr is an expression language and expression evaluation for Go. Prior to version 1.17.0, if the Expr expression parser is given an unbounded input string, it will attempt to compile the entire string and generate an Abstract Syntax Tree (AST) node for each part of the expression. In scenarios where input size isn’t limited, a malicious or inadvertent extremely large expression can consume excessive memory as the parser builds a huge AST. This can ultimately lead to*excessive memory usage and an Out-Of-Memory (OOM) crash of the process. This issue is relatively uncommon and will only manifest when there are no restrictions on the input size, i.e. the expression length is allowed to grow arbitrarily large. In typical use cases where inputs are bounded or validated, this problem would not occur. The problem has been patched in the latest versions of the Expr library. The fix introduces compile-time limits on the number of AST nodes and memory usage during parsing, preventing any single expression from exhausting resources. Users should upgrade to Expr version 1.17.0 or later, as this release includes the new node budget and memory limit safeguards. Upgrading to v1.17.0 ensures that extremely deep or large expressions are detected and safely aborted during compilation, avoiding the OOM condition. For users who cannot immediately upgrade, the recommended workaround is to impose an input size restriction before parsing. In practice, this means validating or limiting the length of expression strings that your application will accept. For example, set a maximum allowable number of characters (or nodes) for any expression and reject or truncate inputs that exceed this limit. By ensuring no unbounded-length expression is ever fed into the parser, one can prevent the parser from constructing a pathologically large AST and avoid potential memory exhaustion. In short, pre-validate and cap input size as a safeguard in the absence of the patch.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 4 betroffen, 12 behoben, 4 nicht betroffen.

Custom Metric Autoscaler operator for Red Hat Openshift BetroffenFix ausstehend custom-metrics-autoscaler/custom-metrics-autoscaler-adapter-rhel8, custom-metrics-autoscaler/custom-metrics-autoscaler-admission-webhooks-rhel9, custom-metrics-autoscaler/custom-metrics-autoscaler-rhel8
Deployment Validation Operator BetroffenFix ausstehend dvo/deployment-validation-rhel8-operator
Red Hat OpenShift AI (RHOAI) BetroffenFix ausstehend rhoai/odh-data-science-pipelines-argo-argoexec-rhel8, rhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel8, rhoai/odh-ml-pipelines-api-server-v2-rhel8, rhoai/odh-ml-pipelines-driver-rhel8, rhoai/odh-ml-pipelines-launcher-rhel8, rhoai/odh-ml-pipelines-persistenceagent-v2-rhel8, rhoai/odh-ml-pipelines-scheduledworkflow-v2-rhel8
Red Hat OpenShift distributed tracing 3 BetroffenFix ausstehend rhosdt/opentelemetry-operator-bundle, rhosdt/opentelemetry-target-allocator-rhel8, rhosdt/tempo-rhel8-operator
Custom Metric Autoscaler operator for Red Hat Openshift 2.15 Behoben custom-metrics-autoscaler RHSA-2025:3993
Red Hat Enterprise Linux AppStream (v. 10) Behoben opentelemetry-collector-0.107.0-9.el10_0 RHSA-2025:7479
Red Hat Enterprise Linux AppStream (v. 9) Behoben opentelemetry-collector-0.107.0-8.el9_5, opentelemetry-collector-0.107.0-8.el9_6 RHSA-2025:3335, RHSA-2025:7407
Red Hat Enterprise Linux AppStream EUS (v.9.4) Behoben opentelemetry-collector-0.107.0-7.el9_4 RHSA-2025:3593
Red Hat OpenShift GitOps 1.15 Behoben openshift-gitops-1/argo-rollouts-rhel8, openshift-gitops-1/argocd-extensions-rhel8, openshift-gitops-1/argocd-rhel8, openshift-gitops-1/argocd-rhel9, openshift-gitops-1/console-plugin-rhel8, openshift-gitops-1/dex-rhel8, openshift-gitops-1/gitops-operator-bundle, openshift-gitops-1/gitops-rhel8, openshift-gitops-1/gitops-rhel8-operator, openshift-gitops-1/must-gather-rhel8 RHSA-2025:7753
Red Hat OpenShift distributed tracing 3.5.3 Behoben rhosdt RHSA-2025:3740, RHSA-2025:3743
Red Hat OpenShift distributed tracing 3.6.0 Behoben rhosdt RHSA-2025:9167
SUSE Linux Enterprise Server 16.0 Behoben govulncheck-vulndb-0.0.20250814T182633-160000.1.2
SUSE Linux Enterprise Server 16.1 Behoben govulncheck-vulndb-0.0.20260916T180043-160100.1.1
SUSE Linux Enterprise Server for SAP applications 16.0 Behoben govulncheck-vulndb-0.0.20250814T182633-160000.1.2
SUSE Linux Enterprise Server for SAP applications 16.1 Behoben govulncheck-vulndb-0.0.20260916T180043-160100.1.1
openSUSE Tumbleweed Behoben argocd-cli-2.14.10-1.1, argocd-cli-bash-completion-2.14.10-1.1, argocd-cli-zsh-completion-2.14.10-1.1, govulncheck-vulndb-0.0.20250318T181448-1.1
Nicht betroffen (4)
Custom Metric Autoscaler operator for Red Hat Openshift 2.15Nicht betroffenverwundbarer Code nicht enthaltencustom-metrics-autoscaler
Red Hat OpenShift distributed tracing 3Nicht betroffenKomponente nicht enthaltenrhosdt/tempo-gateway-opa-rhel8, rhosdt/tempo-gateway-rhel8, rhosdt/tempo-jaeger-query-rhel8, rhosdt/tempo-operator-bundle, rhosdt/tempo-query-rhel8
Red Hat OpenShift distributed tracing 3.5.3Nicht betroffenverwundbarer Code nicht enthaltenrhosdt
Red Hat OpenShift distributed tracing 3.6.0Nicht betroffenverwundbarer Code nicht enthaltenrhosdt

Betroffene Pakete im beobachteten Stack

Red Hat:enterprise_linux:10.0opentelemetry-collector0:0.107.0-9.el10_0CVE-2025-29786
Red Hat:enterprise_linux:10.0opentelemetry-collector0:0.107.0-9.el10_0RHSA-2025:7479 (über RHSA-2025:7479)
Red Hat:enterprise_linux:9::appstreamopentelemetry-collector0:0.107.0-8.el9_5CVE-2025-29786
Red Hat:enterprise_linux:9::appstreamopentelemetry-collector0:0.107.0-8.el9_6CVE-2025-29786
Red Hat:enterprise_linux:9::appstreamopentelemetry-collector0:0.107.0-8.el9_5RHSA-2025:3335 (über RHSA-2025:3335)
Red Hat:enterprise_linux:9::appstreamopentelemetry-collector0:0.107.0-8.el9_6RHSA-2025:7407 (über RHSA-2025:7407)
Red Hat:rhel_eus:9.4::appstreamopentelemetry-collector0:0.107.0-7.el9_4CVE-2025-29786
Red Hat:rhel_eus:9.4::appstreamopentelemetry-collector0:0.107.0-7.el9_4RHSA-2025:3593 (über RHSA-2025:3593)
Weitere betroffene Pakete (18)
Azure Linux:2coredns1.11.1-18AZL-58848
Azure Linux:3coredns1.11.4-5AZL-58872
Azure Linux:3ig0.37.0-3AZL-58857
Azure Linux:3keda2.14.1-5AZL-58861
CVEexpr-lang/exprkein Fix bekanntCVE-2025-29786
Debian:12golang-github-antonmedv-exprkein Fix bekanntDEBIAN-CVE-2025-29786
Debian:13golang-github-antonmedv-exprkein Fix bekanntDEBIAN-CVE-2025-29786
Debian:14golang-github-antonmedv-exprkein Fix bekanntDEBIAN-CVE-2025-29786
Gogithub.com/expr-lang/expr1.17.0GHSA-93mq-9ffx-83m2
Gogithub.com/expr-lang/expr1.17.0GO-2025-3525
Rocky Linux:10opentelemetry-collector0:0.107.0-9.el10_0RLSA-2025:7479
Ubuntu:22.04:LTSgolang-github-antonmedv-exprkein Fix bekanntUBUNTU-CVE-2025-29786
Ubuntu:24.04:LTSgolang-github-antonmedv-exprkein Fix bekanntUBUNTU-CVE-2025-29786
Ubuntu:25.10golang-github-antonmedv-exprkein Fix bekanntUBUNTU-CVE-2025-29786
Ubuntu:26.04:LTSgolang-github-antonmedv-exprkein Fix bekanntUBUNTU-CVE-2025-29786
Ubuntu:26.10golang-github-antonmedv-exprkein Fix bekanntUBUNTU-CVE-2025-29786
openSUSE:Tumbleweedargocd-cli2.14.10-1.1openSUSE-SU-2025:15006-1
openSUSE:Tumbleweedgovulncheck-vulndb0.0.20250318T181448-1.1openSUSE-SU-2025:14910-1

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.