CVE-2023-27891
Rami Pretix 1.16.0 – 4.15.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS 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-27891 is a high-severity Insufficient Session Expiration (CWE-613) vulnerability in Rami Pretix. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Cloud Accounts (T1078.004); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-0208
Vulnerability Data
rami.io pretix before 4.17.1 allows OAuth application authorization from a logged-out session. The fixed versions are 4.15.1, 4.16.1, and 4.17.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
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.
Locks the device (typically after inactivity) until re-authentication, addressing insufficient session expiration by preventing indefinite access.
Automatically terminating sessions after a defined period directly enforces session expiration, preventing indefinite session lifetimes that attackers can exploit.
Re-authentication after inactivity or time-based triggers prevents indefinite use of potentially hijacked or stale sessions.
Terminating sessions and network connections upon completion prevents insufficient session expiration.
Directly enforces termination of network sessions after inactivity or end-of-session, preventing indefinite session lifetime.
Consistent clocks across systems allow session expiration and timeout enforcement to function as intended in distributed environments.
When the non-persistent artifact is a session or connection, mandatory termination implements the missing expiration that CWE-613 describes.
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.
Credential lifecycle management directly includes enforcing session expiration to prevent reuse.
Authorization policy enforcement and review covers terminating stale sessions to limit access scope.
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.
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.
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.
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.
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.
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.
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.