Skip to content
Fencer Intel
medium 6.1

CVE-2024-29041 json

Express.js Open Redirect in malformed URLs

published 2y ago modified last mo. also EUVD-2024-1007 , GHSA-rv95-896h-c2vc

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

Express.js minimalist web framework for node. Versions of Express.js prior to 4.19.0 and all pre-release alpha and beta versions of 5.0 are affected by an open redirect vulnerability using malformed URLs. When a user of Express performs a redirect using a user-provided URL Express performs an encode [using `encodeurl`](https://github.com/pillarjs/encodeurl) on the contents before passing it to the `location` header. This can cause malformed URLs to be evaluated in unexpected ways by common redirect allow list implementations in Express applications, leading to an Open Redirect via bypass of a properly implemented allow list. The main method impacted is `res.location()` but this is also called from within `res.redirect()`. The vulnerability is fixed in 4.19.2 and 5.0.0-beta.3.

Patch / fix

  • npm express 4.19.2, 5.0.0-beta.3
  • expressjs express 4.19.0, 5.0.0-beta.3
  • openjsf express 4.19.0, 5.0.0-beta.3
  • node-express Debian 14, Debian 13 4.19.2+~cs8.36.21-1

debian advisories DEBIAN-CVE-2024-29041

  • node-express Ubuntu Pro 16.04 LTS 4.1.1~dfsg-1ubuntu0.16.04.1~esm1
  • node-express Ubuntu Pro 18.04 LTS 4.1.1~dfsg-1ubuntu0.18.04.1~esm1
  • node-express Ubuntu Pro 20.04 LTS 4.17.1-2ubuntu0.1~esm1
  • node-express Ubuntu Pro 22.04 LTS 4.17.3+~4.17.13-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2024-29041

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • reaper CBL-Mariner 2.0 3.1.1-9

azure linux advisories AZL-37137

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2024-29041 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-29041 updated cvss 6.1

express: cause malformed URLs to be evaluated

  • Red Hat A-MQ Interconnect 1 qpid-dispatch
    affected: workaround, no fix available “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/logging-view-plugin-rhel9 Red Hat Migration Toolkit for Applications 6 mta/mta-ui-rhel8, python-pymata-express
    affected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Migration Toolkit for Applications 7 mta/mta-ui-rhel8, mta/mta-cli-rhel9
    affected: workaround, no fix available, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Migration Toolkit for Runtimes python-pymata-express
    affected: workaround, no fix available “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Node HealthCheck Operator workload-availability/node-remediation-console-rhel8
    affected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat 3scale API Management Platform 2 3scale-amp2/system-rhel7
    affected: workaround, no fix available “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Advanced Cluster Security 3 advanced-cluster-security/rhacs-main-rhel8, advanced-cluster-security/rhacs-roxctl-rhel8, advanced-cluster-security/rhacs-rhel8-operator, advanced-cluster-security/rhacs-central-db-rhel8
    affected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Advanced Cluster Security 4 advanced-cluster-security/rhacs-main-rhel8, advanced-cluster-security/rhacs-roxctl-rhel8, advanced-cluster-security/rhacs-rhel8-operator, advanced-cluster-security/rhacs-central-db-rhel8, advanced-cluster-security/rhacs-scanner-v4-rhel8
    affected: workaround, no fix available, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
show 21 more
  • Red Hat Developer Hub 1 rhdh/rhdh-hub-rhel9 Red Hat Discovery 1 discovery-server-container
    affected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Enterprise Linux 6 firefox, thunderbird
    affected: workaround, no fix available “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Enterprise Linux 7 firefox, thunderbird
    affected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Enterprise Linux 8 cldr-emoji-annotation
    affected: workaround, no fix available “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat OpenShift AI (RHOAI) odh-operator-container, odh-dashboard-container Red Hat OpenShift Container Platform 3.11 openshift3/ose-console Red Hat OpenShift Container Platform 4 openshift4/ose-console, openshift4/ose-monitoring-plugin-rhel9, openshift4/nmstate-console-plugin-rhel9, openshift4/ose-networking-console-plugin-rhel9
    affected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Openshift Container Storage 4 ocs4/mcg-core-rhel8
    affected: workaround, no fix available “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat OpenShift Data Science (RHODS) rhods/odh-rhel8-operator, rhods/odh-dashboard-rhel8 Red Hat OpenShift distributed tracing 2 rhosdt/jaeger-query-rhel8, rhosdt/jaeger-all-in-one-rhel8 Red Hat OpenShift distributed tracing 3 rhosdt/jaeger-query-rhel8, rhosdt/jaeger-all-in-one-rhel8
    affected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat OpenShift GitOps openshift-gitops-1/argocd-rhel8, openshift-gitops-1/argo-rollouts-rhel8, openshift-gitops-1/console-plugin-rhel8, openshift-gitops-argocd-rhel9-container Red Hat OpenShift Virtualization 4 container-native-virtualization/kubevirt-console-plugin, container-native-virtualization/kubevirt-console-plugin-rhel9
    affected: workaround, no fix available, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Quay 3 quay/quay-rhel8
    affected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Satellite 6 qpid-dispatch, libqpid-dispatch, qpid-dispatch-tools, qpid-dispatch-router
    affected: workaround, no fix available “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat NETOBSERV 1.6 for RHEL 9 network-observability/network-observability-cli-rhel9 v1.6.0-66, network-observability/network-observability-operator-bundle 1.6.0-78, network-observability/network-observability-rhel9-operator v1.6.0-66, network-observability/network-observability-ebpf-agent-rhel9 v1.6.0-66, network-observability/network-observability-console-plugin-rhel9 v1.6.0-66, network-observability/network-observability-flowlogs-pipeline-rhel9 v1.6.0-66
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3868
  • Red Hat OpenShift Pipelines version 1.16 for RHEL 8 openshift-pipelines/pipelines-nop-rhel8 v1.16.0-7, openshift-pipelines/pipelines-events-rhel8 v1.16.0-7, openshift-pipelines/pipelines-hub-ui-rhel8 v1.16.0-3, openshift-pipelines/pipelines-cli-tkn-rhel8 v1.16.0-7, openshift-pipelines/pipelines-hub-api-rhel8 v1.16.0-3, openshift-pipelines/pipelines-webhook-rhel8 v1.16.0-7, +22 more
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHEA-2024:7870
  • Red Hat build of Apicurio Registry 2.6.1 GA
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:4873
  • Red Hat Migration Toolkit 1.8 rhmtc/openshift-migration-ui-rhel8 v1.8.4-10
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:7164
  • Red Hat RHODF 4.14 for RHEL 9 odf4/mcg-core-rhel9 v4.14.11-1, odf4/odf-console-rhel9 v4.14.18-3, odf4/ocs-client-console-rhel9 v4.14.18-2, odf4/odf-multicluster-console-rhel9 v4.14.18-2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:7624
  • Red Hat RHODF 4.15 for RHEL 9 odf4/odf-console-rhel9 v4.15.14-2, odf4/ocs-client-console-rhel9 v4.15.14-2, odf4/odf-multicluster-console-rhel9 v4.15.14-2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:8544
  • Red Hat RHODF 4.16 for RHEL 9 odf4/odf-console-rhel9 v4.16.10-4, odf4/ocs-client-console-rhel9 v4.16.10-4, odf4/odf-multicluster-console-rhel9 v4.16.10-3
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:8479
  • Red Hat RHODF 4.17 for RHEL 9 odf4/odf-console-rhel9 v4.17.7-2, odf4/ocs-client-console-rhel9 v4.17.7-2, odf4/odf-multicluster-console-rhel9 v4.17.7-2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:8059
  • Red Hat RHODF 4.18 for RHEL 9 odf4/odf-console-rhel9 v4.18.2-7, odf4/ocs-client-console-rhel9 v4.18.2-8, odf4/odf-multicluster-console-rhel9 v4.18.2-8
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:4511
  • Red Hat RHOSSM 2.6 for RHEL 8 openshift-service-mesh/pilot-rhel8 2.6.1-7, openshift-service-mesh/kiali-rhel8 1.89.1-3, openshift-service-mesh/grafana-rhel8 2.6.1-6, openshift-service-mesh/istio-cni-rhel8 2.6.1-7, openshift-service-mesh/ratelimit-rhel8 2.6.1-6, openshift-service-mesh/kiali-ossmc-rhel8 1.89.0-2, +3 more Red Hat RHOSSM 2.6 for RHEL 9 openshift-service-mesh/proxyv2-rhel9 2.6.1-4
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:6211
  • Red Hat Cryostat 2 python-pymata-express Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/kibana6-rhel8 Red Hat Migration Toolkit for Virtualization migration-toolkit-virtualization/mtv-console-plugin-rhel9 Red Hat Multicluster Engine for Kubernetes multicluster-engine/multicluster-engine-console-mce-rhel9
    not affected: vulnerable code not present

28 more not affected in the full advisory

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
GitHub 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm express
<4.19.2
>=5.0.0-alpha.1, <5.0.0-beta.3
4.19.2
5.0.0-beta.3

Affected products

  • expressjs express

Classification

Weakness
  • CWE-601 URL Redirection to Untrusted Site
  • CWE-1286 Improper Validation of Syntactic Correctness of Input
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of expressjs/express published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.