BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-29041High confidence

Express.js Open Redirect in malformed URLs

expressjs · express

Official source article: GitHub GHSA-RV95-896H-C2VC ↗. Check the applicable product and release in the original source.

6.1MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.79% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs expressjs express and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenode-expressVendor fix publishedDebian records a fixed source-package version for this release.4.19.2+~cs8.36.21-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcenode-expressAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcenode-expressVendor fix publishedDebian records a fixed source-package version for this release.4.19.2+~cs8.36.21-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcenode-expressVendor fix publishedDebian records a fixed source-package version for this release.4.19.2+~cs8.36.21-1Debian Security Tracker ↗Source updated 6 Oct 2026
Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmexpress< 4.19.24.19.2GitHub advisory ↗upstream repository advisory · 20 Dec 2025
npmexpress>= 5.0.0-alpha.1, < 5.0.0-beta.35.0.0-beta.3GitHub advisory ↗upstream repository advisory · 20 Dec 2025
npmexpressSEMVER: introduced 0; fixed 4.19.24.19.2OSV record ↗aggregator derived · 10 Sep 2026
npmexpressSEMVER: introduced 5.0.0-alpha.1; fixed 5.0.0-beta.35.0.0-beta.3OSV record ↗aggregator derived · 10 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-29041 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityexpress: cause malformed URLs to be evaluated
59 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • qpid-dispatch.src as a component of A-MQ Interconnect 1
  • openshift-logging/logging-view-plugin-rhel8 as a component of Logging Subsystem for Red Hat OpenShift
  • express.src as a component of Migration Toolkit for Applications 6
  • mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 6
  • mta/mta-cli-rhel9 as a component of Migration Toolkit for Applications 7
  • mta/mta-ui-rhel9 as a component of Migration Toolkit for Applications 7
  • express.src as a component of Migration Toolkit for Runtimes
  • workload-availability/node-remediation-console-rhel8 as a component of Node HealthCheck Operator
  • 3scale-amp-system-container as a component of Red Hat 3scale API Management Platform 2
  • advanced-cluster-security/rhacs-central-db-rhel8 as a component of Red Hat Advanced Cluster Security 3
  • advanced-cluster-security/rhacs-main-rhel8 as a component of Red Hat Advanced Cluster Security 3
  • advanced-cluster-security/rhacs-rhel8-operator as a component of Red Hat Advanced Cluster Security 3
Summary
A flaw was found in the Express.js minimalist web framework for node. Upstream versions of Express.js before 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 issue 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 upstream version 4.19.2 and 5.0.0-beta.3.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-1007

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → URL Redirection to Untrusted Site ('Open Redirect') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-601 ↗

CWE-601: URL Redirection to Untrusted Site ('Open Redirect'). The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-601
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0168Oracle JD Edwards: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle JD Edwards ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2024-1590HCL BigFix: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in HCL BigFix ausnutzen, um einen Denial of Service Angriff durchzuführen, ertrauliche Informationen preiszugeben, Daten zu manipulieren und Sicherheitsmaßnahmen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2025-0010HCL BigFix Server Automation: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in HCL BigFix Server Automation ausnutzen, um Dateien zu manipulieren, vertrauliche Informationen preiszugeben und Phishing-Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-2036Red Hat OpenShift: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen

Ein entfernter anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu erzeugen.

Official advisory ↗
BSI · German · WID-SEC-2024-0956IBM App Connect Enterprise: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um Phishing-Angriffe durchzuführen, Sicherheitsmaßnahmen zu umgehen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240327Security Bulletin 27 Mar 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 27 Mar 2024, published on 27 March 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1233Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2022-37620 Référence CVE CVE-2022-46175 https://www.cve.org/CVERecord?id=CVE-2022-46175 Référence CVE CVE-2022-46337 https://www.cve.org/CVERecord?id=CVE-2022-46337 Référence CVE CVE-2023-0842 https://www.cve.org/CVERecord?id=CVE-2023-0842 Référence CVE CVE-2023-26158 https://www.cve.org/CVERecord?id=CVE-2023-26158 Référence CVE CVE-2023-44270 https://www.cve.org/CVERecord?id=CVE-2023-44270 Référence CVE CVE-2023-45133 https://www.cve.org/CVERecord?id=CVE-2023-45133 Référence CVE CVE-2024-21538 https://www.cve.org/CVERecord?id=CVE-2024-21538 Référence CVE CVE-2024-22195 https://www.cve.org/CVERecord?id=CVE-2024-22195 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-34064 https://www.cve.org/CVERecord?id=CVE-2024-34064 Référence CVE CVE-2024-37890 https://www.cve.org/CVERecord?id=CVE-2024-37890 Référence CVE CVE-2024-4067 https://www.cve.org/CVERecord?id=CVE-2024-4067 Référence CVE CVE-2024-4068 https://www.cve.org/CVERecord?id=CVE-2024-4068 Référence CVE CVE-2024-43796 https://www.cve.org/CVERecord?id=CVE-2024-43796 Référence CVE CVE-2024-43799 https://www.cve.org/CVERecord?id=CVE-2024-43799 Référence CVE CVE-2024-43800 https://www.cve.org/CVERecord?id=CVE-2024-43800 Référence CVE CVE-2024-45590 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0627Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2022-25883 Référence CVE CVE-2023-26115 https://www.cve.org/CVERecord?id=CVE-2023-26115 Référence CVE CVE-2023-26136 https://www.cve.org/CVERecord?id=CVE-2023-26136 Référence CVE CVE-2023-32305 https://www.cve.org/CVERecord?id=CVE-2023-32305 Référence CVE CVE-2023-43804 https://www.cve.org/CVERecord?id=CVE-2023-43804 Référence CVE CVE-2023-44270 https://www.cve.org/CVERecord?id=CVE-2023-44270 Référence CVE CVE-2023-45133 https://www.cve.org/CVERecord?id=CVE-2023-45133 Référence CVE CVE-2023-46298 https://www.cve.org/CVERecord?id=CVE-2023-46298 Référence CVE CVE-2024-1135 https://www.cve.org/CVERecord?id=CVE-2024-1135 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-52046 https://www.cve.org/CVERecord?id=CVE-2024-52046 Référence CVE CVE-2024-5629 https://www.cve.org/CVERecord?id=CVE-2024-5629 Référence CVE CVE-2024-6827 https://www.cve.org/CVERecord?id=CVE-2024-6827 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2025-21587 https://www.cve.org/CVERecord?id=CVE-2025-21587 Référence CVE CVE-2025-2900 https://www.cve.org/CVERecord?id=CVE-2025-2900 Référence CVE CVE-2025-30698 https://www.cve.org/CVERecord?id=CVE-2025-30698 Référence CVE CVE-2025-36097 https://www.cve.org/CVERecord?id=CVE-2025

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0233Multiples vulnérabilités dans les produits IBM

VERecord?id=CVE-2018-8032 Référence CVE CVE-2019-0227 https://www.cve.org/CVERecord?id=CVE-2019-0227 Référence CVE CVE-2021-38986 https://www.cve.org/CVERecord?id=CVE-2021-38986 Référence CVE CVE-2022-22321 https://www.cve.org/CVERecord?id=CVE-2022-22321 Référence CVE CVE-2023-28439 https://www.cve.org/CVERecord?id=CVE-2023-28439 Référence CVE CVE-2023-46136 https://www.cve.org/CVERecord?id=CVE-2023-46136 Référence CVE CVE-2024-1135 https://www.cve.org/CVERecord?id=CVE-2024-1135 Référence CVE CVE-2024-1681 https://www.cve.org/CVERecord?id=CVE-2024-1681 Référence CVE CVE-2024-22195 https://www.cve.org/CVERecord?id=CVE-2024-22195 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-34064 https://www.cve.org/CVERecord?id=CVE-2024-34064 Référence CVE CVE-2024-34069 https://www.cve.org/CVERecord?id=CVE-2024-34069 Référence CVE CVE-2024-35195 https://www.cve.org/CVERecord?id=CVE-2024-35195 Référence CVE CVE-2024-3651 https://www.cve.org/CVERecord?id=CVE-2024-3651 Référence CVE CVE-2024-37891 https://www.cve.org/CVERecord?id=CVE-2024-37891 Référence CVE CVE-2024-39689 https://www.cve.org/CVERecord?id=CVE-2024-39689 Référence CVE CVE-2024-4340 https://www.cve.org/CVERecord?id=CVE-2024-4340 Référence CVE CVE-2024-43796 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0106Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-26615 Référence CVE CVE-2024-26851 https://www.cve.org/CVERecord?id=CVE-2024-26851 Référence CVE CVE-2024-26924 https://www.cve.org/CVERecord?id=CVE-2024-26924 Référence CVE CVE-2024-26961 https://www.cve.org/CVERecord?id=CVE-2024-26961 Référence CVE CVE-2024-26976 https://www.cve.org/CVERecord?id=CVE-2024-26976 Référence CVE CVE-2024-27017 https://www.cve.org/CVERecord?id=CVE-2024-27017 Référence CVE CVE-2024-27062 https://www.cve.org/CVERecord?id=CVE-2024-27062 Référence CVE CVE-2024-27268 https://www.cve.org/CVERecord?id=CVE-2024-27268 Référence CVE CVE-2024-28849 https://www.cve.org/CVERecord?id=CVE-2024-28849 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-29180 https://www.cve.org/CVERecord?id=CVE-2024-29180 Référence CVE CVE-2024-29415 https://www.cve.org/CVERecord?id=CVE-2024-29415 Référence CVE CVE-2024-29736 https://www.cve.org/CVERecord?id=CVE-2024-29736 Référence CVE CVE-2024-31141 https://www.cve.org/CVERecord?id=CVE-2024-31141 Référence CVE CVE-2024-32007 https://www.cve.org/CVERecord?id=CVE-2024-32007 Référence CVE CVE-2024-33883 https://www.cve.org/CVERecord?id=CVE-2024-33883 Référence CVE CVE-2024-35839 https://www.cve.org/CVERecord?id=CVE-2024-35839 Référence CVE CVE-2024-35898 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1103Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-26308 Référence CVE CVE-2024-27980 https://www.cve.org/CVERecord?id=CVE-2024-27980 Référence CVE CVE-2024-27982 https://www.cve.org/CVERecord?id=CVE-2024-27982 Référence CVE CVE-2024-27983 https://www.cve.org/CVERecord?id=CVE-2024-27983 Référence CVE CVE-2024-28176 https://www.cve.org/CVERecord?id=CVE-2024-28176 Référence CVE CVE-2024-28757 https://www.cve.org/CVERecord?id=CVE-2024-28757 Référence CVE CVE-2024-28849 https://www.cve.org/CVERecord?id=CVE-2024-28849 Référence CVE CVE-2024-28863 https://www.cve.org/CVERecord?id=CVE-2024-28863 Référence CVE CVE-2024-29025 https://www.cve.org/CVERecord?id=CVE-2024-29025 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-29131 https://www.cve.org/CVERecord?id=CVE-2024-29131 Référence CVE CVE-2024-29133 https://www.cve.org/CVERecord?id=CVE-2024-29133 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=CVE-2024-29857 Référence CVE CVE-2024-29896 https://www.cve.org/CVERecord?id=CVE-2024-29896 Référence CVE CVE-2024-30171 https://www.cve.org/CVERecord?id=CVE-2024-30171 Référence CVE CVE-2024-30172 https://www.cve.org/CVERecord?id=CVE-2024-30172 Référence CVE CVE-2024-33883 https://www.cve.org/CVERecord?id=CVE-2024-33883 Référence CVE CVE-2024-34102 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0726Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et une injection de code indirecte à distance (XSS).

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0692Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-25024 Référence CVE CVE-2024-25062 https://www.cve.org/CVERecord?id=CVE-2024-25062 Référence CVE CVE-2024-25629 https://www.cve.org/CVERecord?id=CVE-2024-25629 Référence CVE CVE-2024-27267 https://www.cve.org/CVERecord?id=CVE-2024-27267 Référence CVE CVE-2024-27982 https://www.cve.org/CVERecord?id=CVE-2024-27982 Référence CVE CVE-2024-27983 https://www.cve.org/CVERecord?id=CVE-2024-27983 Référence CVE CVE-2024-28176 https://www.cve.org/CVERecord?id=CVE-2024-28176 Référence CVE CVE-2024-28182 https://www.cve.org/CVERecord?id=CVE-2024-28182 Référence CVE CVE-2024-28799 https://www.cve.org/CVERecord?id=CVE-2024-28799 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-29415 https://www.cve.org/CVERecord?id=CVE-2024-29415 Référence CVE CVE-2024-2961 https://www.cve.org/CVERecord?id=CVE-2024-2961 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=CVE-2024-29857 Référence CVE CVE-2024-30171 https://www.cve.org/CVERecord?id=CVE-2024-30171 Référence CVE CVE-2024-30172 https://www.cve.org/CVERecord?id=CVE-2024-30172 Référence CVE CVE-2024-30260 https://www.cve.org/CVERecord?id=CVE-2024-30260 Référence CVE CVE-2024-30261 https://www.cve.org/CVERecord?id=CVE-2024-30261 Référence CVE CVE-2024-33599 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0630Multiples vulnérabilités dans IBM QRadar

Record?id=CVE-2023-6129 Référence CVE CVE-2024-0553 https://www.cve.org/CVERecord?id=CVE-2024-0553 Référence CVE CVE-2024-0567 https://www.cve.org/CVERecord?id=CVE-2024-0567 Référence CVE CVE-2024-27088 https://www.cve.org/CVERecord?id=CVE-2024-27088 Référence CVE CVE-2024-27982 https://www.cve.org/CVERecord?id=CVE-2024-27982 Référence CVE CVE-2024-27983 https://www.cve.org/CVERecord?id=CVE-2024-27983 Référence CVE CVE-2024-28834 https://www.cve.org/CVERecord?id=CVE-2024-28834 Référence CVE CVE-2024-28835 https://www.cve.org/CVERecord?id=CVE-2024-28835 Référence CVE CVE-2024-28863 https://www.cve.org/CVERecord?id=CVE-2024-28863 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-29415 https://www.cve.org/CVERecord?id=CVE-2024-29415 Référence CVE CVE-2024-2961 https://www.cve.org/CVERecord?id=CVE-2024-2961 Référence CVE CVE-2024-31905 https://www.cve.org/CVERecord?id=CVE-2024-31905 Référence CVE CVE-2024-33599 https://www.cve.org/CVERecord?id=CVE-2024-33599 Référence CVE CVE-2024-33600 https://www.cve.org/CVERecord?id=CVE-2024-33600 Référence CVE CVE-2024-33601 https://www.cve.org/CVERecord?id=CVE-2024-33601 Référence CVE CVE-2024-33602 https://www.cve.org/CVERecord?id=CVE-2024-33602 Référence CVE CVE-2024-4067 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0579Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-26461 Référence CVE CVE-2024-27088 https://www.cve.org/CVERecord?id=CVE-2024-27088 Référence CVE CVE-2024-27270 https://www.cve.org/CVERecord?id=CVE-2024-27270 Référence CVE CVE-2024-28102 https://www.cve.org/CVERecord?id=CVE-2024-28102 Référence CVE CVE-2024-28176 https://www.cve.org/CVERecord?id=CVE-2024-28176 Référence CVE CVE-2024-28182 https://www.cve.org/CVERecord?id=CVE-2024-28182 Référence CVE CVE-2024-28834 https://www.cve.org/CVERecord?id=CVE-2024-28834 Référence CVE CVE-2024-28849 https://www.cve.org/CVERecord?id=CVE-2024-28849 Référence CVE CVE-2024-28863 https://www.cve.org/CVERecord?id=CVE-2024-28863 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-2961 https://www.cve.org/CVERecord?id=CVE-2024-2961 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=CVE-2024-29857 Référence CVE CVE-2024-30171 https://www.cve.org/CVERecord?id=CVE-2024-30171 Référence CVE CVE-2024-30172 https://www.cve.org/CVERecord?id=CVE-2024-30172 Référence CVE CVE-2024-3019 https://www.cve.org/CVERecord?id=CVE-2024-3019 Référence CVE CVE-2024-33599 https://www.cve.org/CVERecord?id=CVE-2024-33599 Référence CVE CVE-2024-33600 https://www.cve.org/CVERecord?id=CVE-2024-33600 Référence CVE CVE-2024-33601 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0514Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-23807 Référence CVE CVE-2024-24549 https://www.cve.org/CVERecord?id=CVE-2024-24549 Référence CVE CVE-2024-24557 https://www.cve.org/CVERecord?id=CVE-2024-24557 Référence CVE CVE-2024-24786 https://www.cve.org/CVERecord?id=CVE-2024-24786 Référence CVE CVE-2024-25026 https://www.cve.org/CVERecord?id=CVE-2024-25026 Référence CVE CVE-2024-27289 https://www.cve.org/CVERecord?id=CVE-2024-27289 Référence CVE CVE-2024-27306 https://www.cve.org/CVERecord?id=CVE-2024-27306 Référence CVE CVE-2024-28180 https://www.cve.org/CVERecord?id=CVE-2024-28180 Référence CVE CVE-2024-28849 https://www.cve.org/CVERecord?id=CVE-2024-28849 Référence CVE CVE-2024-29041 https://www.cve.org/CVERecord?id=CVE-2024-29041 Référence CVE CVE-2024-29131 https://www.cve.org/CVERecord?id=CVE-2024-29131 Référence CVE CVE-2024-29133 https://www.cve.org/CVERecord?id=CVE-2024-29133 Référence CVE CVE-2024-29180 https://www.cve.org/CVERecord?id=CVE-2024-29180 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=CVE-2024-29857 Référence CVE CVE-2024-30171 https://www.cve.org/CVERecord?id=CVE-2024-30171 Référence CVE CVE-2024-30172 https://www.cve.org/CVERecord?id=CVE-2024-30172 Référence CVE CVE-2024-30251 https://www.cve.org/CVERecord?id=CVE-2024-30251 Référence CVE CVE-2024-34351 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-029607Open JS Foundation の Node.js 用 express におけるオープンリダイレクトの脆弱性

Open JS Foundation の Node.js 用 express には、オープンリダイレクトの脆弱性、入力の構文的正当性の検証に関する脆弱性が存在します。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2025-0026Kwetsbaarheden verholpen in Oracle JD Edwards

De kwetsbaarheden in Oracle JD Edwards EnterpriseOne Tools stellen ongeauthenticeerde kwaadwillenden in staat om het systeem te compromitteren via HTTP-verzoeken. Dit kan leiden tot ongeautoriseerde toegang tot kritieke gegevens en gegevenswijzigingen.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 25 Mar 2024 · Last source change 2 Aug 2024, 01:03 UTC · CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-1007
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    >=4.14.0, <4.19.0; >=5.0.0-alpha.1, <5.0.0-beta.3 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    >=4.14.0, <4.19.0; >=5.0.0-alpha.1, <5.0.0-beta.3 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-29041 · cve.blacktree.nl