Security Resilience

CVE-2024-41763

Crypto Weakness in Ibm Engineering Lifecycle Optimization Publishing 7.0.2 … 7.0.3

Published
04 January 2025
Modified
21 March 2025
Patch / advisory
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0021 10th percentile
Risk Priority 44 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-41763 is a medium-severity Use of a Broken or Risky Cryptographic Algorithm (CWE-327) vulnerability in Ibm Engineering Lifecycle Optimization Publishing. Its CVSS base score is 5.9 (Medium).

Operationally, ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-41763 is a cryptographic weakness in IBM Engineering Lifecycle Optimization - Publishing versions 7.0.2 and 7.0.3, where weaker than expected cryptographic algorithms are used. This flaw, published on 2025-01-04, is categorized under CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) and carries a CVSS v3.1 base score of 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating medium severity primarily due to high confidentiality impact.

An unauthenticated attacker (PR:N) with network access (AV:N) could potentially exploit this vulnerability to decrypt highly sensitive information. The attack requires high complexity (AC:H) and no user interaction (UI:N), with no impact on integrity or availability, but successful exploitation would grant high-level access to confidential data (C:H) in an unchanged scope (S:U).

IBM provides details on the vulnerability, including mitigation and patch information, in their security advisory at https://www.ibm.com/support/pages/node/7180204.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Engineering Lifecycle Optimization - Publishing 7.0.2 and 7.0.3 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-13916Same product: Linux Linux Kernel
CVE-2024-49784Same product: Linux Linux Kernel
CVE-2023-45188Same product: Ibm Engineering Lifecycle Optimization Publishing
CVE-2024-39745Same product: Linux Linux Kernel
CVE-2024-45671Same product: Linux Linux Kernel
CVE-2023-27555Same product: Linux Linux Kernel
CVE-2022-47986Same product: Linux Linux Kernel
CVE-2023-38738Same product: Linux Linux Kernel
CVE-2024-45643Same product: Linux Linux Kernel
CVE-2025-36161Same product: Linux Linux Kernel

Affected Assets

ibm
engineering lifecycle optimization publishing
7.0.2, 7.0.3

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-13 requires selection and implementation of specific cryptography types, directly stopping use of broken algorithms.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.31 only requires identifying, reviewing and considering legal/regulatory/contractual requirements (including crypto restrictions); it does not itself stop use of a broken algorithm or block its exploitation

blocks

A.5.6 only promotes membership in groups to receive early warnings, advisories, and specialist advice about vulnerabilities (including risky crypto); it does not stop exploitation of an already-present broken algorithm, which requires other controls (e.g. A.8.24) to act.

blocks

A.8.24's policy, algorithm selection, strength/quality rules, approved standards and key management directly stop use of broken/risky algorithms in most cases; the bounded remainder is non-compliant implementations or legacy systems grandfathered under the clause's own regulatory and transition guidance.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-327, a class-level weakness. Rules are authored against its narrower children: CWE-328, CWE-780, CWE-1240.

References