Skip to main content
VulnerabilityPublished Updated

CVE-2024-51464: IBM · Authentication Bypass Using an Alternate Path or Channel

Affects IBMSource CVE Database V5

0

Public exploit available (Exploit-DB) · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 21 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

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

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by IBM Corporation

    , 54 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. First Exploit-DB entry (opens in a new tab)

    IBMi Navigator 7.5 - HTTP Security Token Bypass

    , 115 days after disclosure

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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBMAffected
  • =7.3
  • =7.4
  • =7.5
Fixed in–

AI-suggested

  1. Monitor IBM’s official security advisories closely and apply patches or updates for IBM i versions 7.3, 7.4, and 7.5 as soon as they are released to address CVE-2024-51464.
  2. Restrict access to the Navigator for i interface using network segmentation, firewall rules, and VPNs to limit exposure to trusted users and networks only.
  3. Enforce strong authentication mechanisms and consider multi-factor authentication (MFA) for all users accessing Navigator for i to reduce the risk of credential compromise.
  4. Implement detailed logging and continuous monitoring of Navigator for i activities to detect anomalous or unauthorized operations indicative of exploitation attempts.
  5. Conduct regular audits of user privileges and Navigator for i configurations to ensure least privilege principles are maintained.
  6. Educate system administrators and users about the risks of credential misuse and the importance of secure access practices.
  7. Temporarily disable or limit Navigator for i functionality if feasible until patches are applied, especially in high-risk environments.
  8. Use intrusion detection/prevention systems (IDS/IPS) tuned to detect suspicious crafted requests targeting Navigator for i endpoints. These targeted mitigations go beyond generic advice by focusing on access control, monitoring, and operational hygiene specific to the IBM i Navigator environment.

Description

IBM i 7.3, 7.4, and 7.5 is vulnerable to bypassing Navigator for i interface restrictions. By sending a specially crafted request, an authenticated attacker could exploit this vulnerability to remotely perform operations that the user is not allowed to perform when using Navigator for i.

References

Community reviews

Loading reviews…