Security Resilience

CVE-2023-50312

Crypto Weakness in Ibm Websphere Application Server 17.0.0.3 – 24.0.0.3

Published
01 March 2024
Modified
23 April 2025
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0059 47th percentile
Risk Priority 42 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-2023-50312 is a medium-severity Use of a Broken or Risky Cryptographic Algorithm (CWE-327) vulnerability in Ibm Websphere Application Server. Its CVSS base score is 5.3 (Medium).

Operationally, ranked at the 47th 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.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM WebSphere Application Server Liberty 17.0.0.3 through 24.0.0.2 could provide weaker than expected security for outbound TLS connections caused by a failure to honor user configuration. IBM X-Force ID: 274711.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-35890Same product: Ibm Websphere Application Server
CVE-2023-50313Same product: Ibm Websphere Application Server
CVE-2026-16192Same product: Ibm Websphere Application Server
CVE-2024-37532Same product: Ibm Websphere Application Server
CVE-2026-14446Same product: Ibm Websphere Application Server
CVE-2026-8620Same product: Ibm Websphere Application Server
CVE-2026-15057Same product: Ibm Websphere Application Server
CVE-2025-36124Same product: Ibm Websphere Application Server
CVE-2023-27554Same product: Ibm Websphere Application Server
CVE-2019-4279Same product: Ibm Websphere Application Server

Affected Assets

ibm
websphere application server
17.0.0.3 — 24.0.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