Skip to main content
CVE-2024-54450VulnerabilityPublished Updated

CVE-2024-54450: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.4 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2024-54450, organizations should implement the following specific measures: 1) Configure Kurmi Provisioning Suite to ignore the X-Forwarded-For header during authentication IP logging unless it is received from trusted, internal proxy servers. 2) If proxies are used, enforce strict validation of the X-Forwarded-For header by allowing only known proxy IPs to set or forward this header. 3) Implement network-level controls such as firewall rules or reverse proxies that strip or validate X-Forwarded-For headers from untrusted sources. 4) Enhance logging and monitoring to detect anomalies in login IP addresses, including sudden changes or suspicious IP values. 5) Conduct regular audits of authentication logs to identify potential spoofing attempts. 6) Engage with Kurmi vendors or support channels to obtain patches or updates addressing this vulnerability as they become available. 7) Educate security teams about this vulnerability to improve incident response and forensic investigations. 8) Consider deploying multi-factor authentication to reduce the risk of account compromise even if IP spoofing occurs. These targeted actions go beyond generic advice by focusing on header validation, network controls, and operational awareness specific to this vulnerability.

Description

An issue was discovered in Kurmi Provisioning Suite 7.9.0.33. If an X-Forwarded-For header is received during authentication, the Kurmi application will record the (possibly forged) IP address mentioned in that header rather than the real IP address that the user logged in from. This fake IP address can later be displayed in the My Account popup that shows the IP address that was used to log in.

References

Community reviews

Loading reviews…