CVE-2024-7254VulnerabilityPublished 17 Dec 2024Updated 30 Oct 2026

Red Hat Security Advisory: Red Hat Trusted Profile Analyzer 1.2.1

Affects Red HatSource GCVE Database

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 22:05 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 2.7% chance of exploitation in 30 days – higher than 86% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Red Hat recommends upgrading existing users of Red Hat Trusted Profile Analyzer from version 1.2.0 to 1.2.1. No other mitigation actions are currently recommended by Red Hat Product Security. Users should refer to the official Red Hat release notes and advisories for further details.

Description

CVE-2024-7254 is a vulnerability affecting Red Hat Trusted Profile Analyzer 1.2.1 and related components. It involves a denial of service (DoS) condition due to an unhandled promise rejection error in the http-proxy-middleware package, triggered by certain path requests. This flaw can cause the Node.js process to crash, resulting in transient service disruption. The impact is rated as moderate by Red Hat because it does not compromise data confidentiality or system integrity, and typical Red Hat environments automatically restart crashed application pods. No fix is explicitly stated in the advisory, but an upgrade from version 1.2.0 to 1.2.1 is recommended. No mitigation beyond upgrading is currently provided by Red Hat.

Impact

An unauthenticated remote attacker can cause a denial of service by crashing the Node.js process running the Red Hat Trusted Profile Analyzer through crafted path requests. This results in transient service disruption but does not affect data confidentiality or system integrity. The impact is limited by automatic pod restarts in typical Red Hat container environments, which reduce downtime and blast radius. There is no indication of privilege escalation or code execution from this vulnerability.

Summary

The vulnerability CVE-2024-7254 affects the Red Hat Trusted Profile Analyzer, specifically related to the http-proxy-middleware package used within it. The flaw is a denial of service caused by an unhandled promise rejection error thrown by the micromatch component during path matching. This error can be exploited by an unauthenticated remote attacker to crash the Node.js backend process by sending crafted requests. Although this causes service termination, it does not allow arbitrary code execution or privilege escalation. Red Hat rates the impact as moderate due to automatic pod restarts in containerized environments limiting disruption. The advisory recommends upgrading from version 1.2.0 to 1.2.1.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1333Inefficient Regular Expression Complexity (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.
Architecture and Design
Use regular expressions that do not support backtracking, e.g. by removing nested quantifiers.
System Configuration
Set backtracking limits in the configuration of the regular expression implementation, such as PHP's pcre.backtrack_limit. Also consider limits on execution time for the process.
Implementation
Do not use regular expressions with untrusted input. If regular expressions must be used, avoid using backtracking in the expression.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
Regular Expression Exponential Blowup (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 30 Oct 2026, 22:05 UTC

WeaknessesCWE-770, CWE-400, CWE-1333

Technical details

References

Community reviews

Related threats