Security Resilience

CVE-2023-22591

Ibm Robotic Process Automation 21.0.1 – 21.0.7.1

Published
15 March 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 3.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.0022 13th percentile
Risk Priority 31 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-22591 is a low-severity Insufficient Session Expiration (CWE-613) vulnerability in Ibm Robotic Process Automation. Its CVSS base score is 3.9 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Cloud Accounts (T1078.004); ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Robotic Process Automation 21.0.1 through 21.0.7 and 23.0.0 through 23.0.1 could allow a user with physical access to the system due to session tokens for not being invalidated after a password reset. IBM X-Force ID: 243710.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1078.004 Cloud Accounts Stealth
Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1548.003 Sudo and Sudo Caching Privilege Escalation
Adversaries may perform sudo caching and/or use the sudoers file to elevate privileges.
T1550.001 Application Access Token Lateral Movement
Adversaries may use stolen application access tokens to bypass the typical authentication process and access restricted accounts, information, or services on remote systems.
T1550.004 Web Session Cookie Lateral Movement
Adversaries can use stolen session cookies to authenticate to web applications and services.
T1584.006 Web Services Resource Development
Adversaries may compromise access to third-party web services that can be used during targeting.
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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-49825Same product: Ibm Robotic Process Automation
CVE-2025-36065Same vendor: Ibm
CVE-2025-25019Same vendor: Ibm
CVE-2023-49881Same vendor: Ibm
CVE-2025-66483Same vendor: Ibm
CVE-2024-22358Same vendor: Ibm
CVE-2023-50936Same vendor: Ibm
CVE-2025-36377Same vendor: Ibm
CVE-2023-26288Same vendor: Ibm
CVE-2026-1272Same vendor: Ibm

Affected Assets

ibm
robotic process automation
21.0.1 — 21.0.7.1 · 23.0.0 — 23.0.2
ibm
robotic process automation as a service
≤ 23.0.2

Mitigating Controls

Likely Mitigating Controls

Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-613

Locks the device (typically after inactivity) until re-authentication, addressing insufficient session expiration by preventing indefinite access.

addresses: CWE-613

Automatically terminating sessions after a defined period directly enforces session expiration, preventing indefinite session lifetimes that attackers can exploit.

addresses: CWE-613

Re-authentication after inactivity or time-based triggers prevents indefinite use of potentially hijacked or stale sessions.

addresses: CWE-613

Terminating sessions and network connections upon completion prevents insufficient session expiration.

addresses: CWE-613

Directly enforces termination of network sessions after inactivity or end-of-session, preventing indefinite session lifetime.

addresses: CWE-613

Consistent clocks across systems allow session expiration and timeout enforcement to function as intended in distributed environments.

addresses: CWE-613

When the non-persistent artifact is a session or connection, mandatory termination implements the missing expiration that CWE-613 describes.

addresses: CWE-613

Timed refresh of session-related information or on-demand generation plus deletion implements proper session expiration.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.AA-01 mostly match
blocks

Credential lifecycle management directly includes enforcing session expiration to prevent reuse.

PR.AA-05 mostly match
blocks

Authorization policy enforcement and review covers terminating stale sessions to limit access scope.

PR.AA-03 partial match
blocks

Authentication mechanisms can incorporate session timeout checks but do not inherently address expiration policy.

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

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's combined programme of code review, static analysis, and penetration testing reaches CWE-613 through both SOURCE (session-timeout configurations and token-expiration logic are visible in code, as the demonstrative example shows) and RUNTIME (a session that fails to expire is observable by waiting and re-using the credential). The remainder is bounded and nameable: session expiration logic that lives in framework defaults not surfaced in the reviewed code, or in distributed token-issuance/validation components where the expiration check is implicit rather than explicit.

removes

A.8.5 items (k) and (l) directly mandate session termination after inactivity and connection duration restrictions, which are the primary mechanisms for session expiration and address the core of CWE-613; applying the clause to a system that lacked these removes the timeout-based weakness, but the CWE has been expanded to include logout invalidation and session fixation variations that A.8.5 does not reach, and non-configurable third-party products (the majority of observed CVE instances) cannot be remediated by this clause alone.

blocks

The user responsibility section's guidance to 'log-off active sessions and terminate services when no longer needed' is a user practice that, when followed, terminates sessions and prevents exploitation of those specific sessions, but it does not address the automatic session expiration logic in the application code where the weakness actually lives, and users do not always follow the practice.

prevents

A.8.28's secure coding principles and standards would include session management requirements (timeouts, invalidation), reducing instances where developers omit session expiration, but the control mandates a practice rather than a mechanism and developers remain fallible; the strongest effect on this weakness comes from A.8.29 testing, consistent with the clause's declared ceiling of partial on this verb.

finds

A.8.8's reach is DISCLOSURE; it finds session-expiration weaknesses where they appear as published advisories in third-party components (the CVE examples above), but most CWE-613 instances live in first-party application code whose session-timeout choices never become CVEs, so the disclosed share is a minority.

removes

A.8.9's configuration templates can specify session timeout values (e.g., web server, application server session-timeout settings) and enforce them on operational systems, removing configuration-level instances of CWE-613 such as the demonstrative web.xml `<session-timeout>-1</session-timeout>` case. However, many CWE-613 instances are code-level defects — SDKs that never set token expiration, custom session handlers without expiration logic, or improper logout invalidation — which configuration management cannot rewrite, leaving a nameable remainder of the weakness class untouched.

References