Cyber Resilience

CVE-2024-45670

Auth Bypass in Ibm Soar ≤ 51.0.2.0

Auth Bypass
Published
14 November 2024
Modified
16 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.0033 25th 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-45670 is a medium-severity Weak Password Recovery Mechanism for Forgotten Password (CWE-640) vulnerability in Ibm Soar. Its CVSS base score is 5.6 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 25th 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 IA-12 (Identity Proofing) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A07:2025 Authentication Failures

EU & UK References

Vulnerability Data

IBM Security SOAR 51.0.1.0 and earlier contains a mechanism for users to recover or change their passwords without knowing the original password, but the user account must be compromised prior to the weak recovery mechanism.

CWE(s)
CWE-640

Related Threats

MITRE ATT&CK Enterprise Techniques

T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
attack.mitre.org →
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-43190Same vendor: Ibm
CVE-2024-25031Same vendor: Ibm
CVE-2025-36064Same vendor: Ibm
CVE-2023-26271Same vendor: Ibm
CVE-2024-22317Same vendor: Ibm
CVE-2023-50326Same vendor: Ibm
CVE-2023-45191Same vendor: Ibm
CVE-2023-38273Same vendor: Ibm
CVE-2024-49342Same vendor: Ibm
CVE-2023-4448Shared CWE-640

Affected Assets

ibm
soar
≤ 51.0.2.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V7.4.3

Mitigating Controls (NIST 800-53 r5) AI

IA-12 Identity Proofing good match

Identity proofing at appropriate assurance levels ensures forgotten-password recovery cannot succeed without strong verification of the user.

IA-5 Authenticator Management good match

Authenticator management requires secure distribution, reset, and verification procedures that directly address weak password recovery flows.

Mitigating Controls (NIST CSF 2.0) AI

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

PR.AA-01 mostly match
prevents

Credential lifecycle management directly includes password reset/recovery flows.

PR.AA-02 mostly match
prevents

Identity proofing is the core control that prevents weak or bypassed recovery mechanisms.

PR.AA-03 partial match
prevents

Authentication policy covers strength/MFA but does not address recovery path weaknesses.

PR.PS-06 partial match
prevents

Secure SDLC reduces implementation flaws but is not specific to password-recovery design.

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.

A.5.17 Authentication information partial match
degrades

Strong authentication-information lifecycle rules directly address weak password-recovery flows.

A.8.25 Secure development life cycle partial match
prevents

Secure-SDLC practices can embed strong recovery design, yet the control is broader than this single weakness.

A.8.26 Application security requirements partial match
prevents

Application-security requirements can mandate secure recovery flows, but the control covers many other requirements.

A.8.28 Secure coding partial match
prevents

Secure-coding standards can prevent weak recovery implementations, yet the control is wider in scope.

A.8.5 Secure authentication partial match
mitigates

Secure-authentication requirements include robust forgotten-password procedures.

References