IBM Entirex vulnerabilities

13 CVEs affecting IBM Entirex, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2025-0759, published 2025-02-27.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

CVE-2024-54169, published 2025-02-27. Medium severity, CVSS 6.5. EPSS: 0.5% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow an authenticated attacker to traverse directories on the system. An attacker could send a specially crafted URL request containing "dot dot" sequences (/../) to view…
CVE-2024-54171, published 2025-02-06. High severity, CVSS 7.1. EPSS: 0.4% chance of exploitation in the next 30 days. IBM EntireX 11.1 is vulnerable to an XML external entity injection (XXE) attack when processing XML data. An authenticated attacker could exploit this vulnerability to expose sensitive information or…
CVE-2024-56812, published 2025-02-27. Medium severity, CVSS 5.5. EPSS: 0.2% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow a local user to obtain sensitive information when a detailed technical error message is returned. This information could be used in further attacks against the system.
CVE-2024-56467, published 2025-02-06. Low severity, CVSS 3.3. EPSS: 0.1% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow a local user to obtain sensitive information when a detailed technical error message is returned. This information could be used in further attacks against the system.
CVE-2025-0158, published 2025-02-06. Medium severity, CVSS 5.5. EPSS: 0.1% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow a local user to cause a denial of service due to an unhandled error and fault isolation.
CVE-2024-56811, published 2025-02-27. Low severity, CVSS 3.3. EPSS: 0.1% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow a local user to obtain sensitive information when a detailed technical error message is returned. This information could be used in further attacks against the system.
CVE-2024-56810, published 2025-02-27. Low severity, CVSS 3.3. EPSS: 0.1% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow a local user to obtain sensitive information when a detailed technical error message is returned. This information could be used in further attacks against the system.
CVE-2024-56496, published 2025-02-27. Low severity, CVSS 3.3. EPSS: 0.1% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow a local user to obtain sensitive information when a detailed technical error message is returned. This information could be used in further attacks against the system.
CVE-2024-56495, published 2025-02-27. Low severity, CVSS 3.3. EPSS: 0.1% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow a local user to obtain sensitive information when a detailed technical error message is returned. This information could be used in further attacks against the system.
CVE-2024-56494, published 2025-02-27. Low severity, CVSS 3.3. EPSS: 0.1% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow a local user to obtain sensitive information when a detailed technical error message is returned. This information could be used in further attacks against the system.

Latest

CVE-2025-0759, published 2025-02-27. Low severity, CVSS 3.3. EPSS: 0.1% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow a local user to unintentionally modify data timestamp integrity due to improper shared resource synchronization.
CVE-2024-56493, published 2025-02-27. Low severity, CVSS 3.3. EPSS: 0.1% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow a local user to obtain sensitive information when a detailed technical error message is returned. This information could be used in further attacks against the system.
CVE-2024-54170, published 2025-02-27. Medium severity, CVSS 5.5. EPSS: 0.1% chance of exploitation in the next 30 days. IBM EntireX 11.1 could allow a local user to cause a denial of service due to use of a regular expression with an inefficient complexity that consumes excessive CPU cycles.