Cyber Resilience

CVE-2024-22590

Published
28 May 2024
Modified
15 April 2026
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS Score 0.0058 45th percentile
Risk Priority 68 floored blend · peak EPSS

Summary

CVE-2024-22590 is a critical-severity Incomplete Internal State Distinction (CWE-372) vulnerability. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 45th 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-24 (Fail in Known State) and AC-12 (Session Termination) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

The TLS engine in Kwik commit 745fd4e2 does not track the current state of the connection. This vulnerability can allow Client Hello messages to be overwritten at any time, including after a connection has been established.

CWE(s)
CWE-372

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
T1556 Modify Authentication Process Defense Impairment
Adversaries may modify authentication mechanisms and processes to access user credentials or enable otherwise unwarranted 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-2023-36834Shared CWE-372
CVE-2026-41340Shared CWE-372
CVE-2023-4012Shared CWE-372
CVE-2026-41388Shared CWE-372
CVE-2026-41300Shared CWE-372
CVE-2023-31127Shared CWE-372

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-24 Fail in Known State good match

Ensures the system enters a predefined safe state on failure, containing damage from any prior state-distinction error.

AC-12 Session Termination partial match

Forces sessions into a known terminated state, limiting the window in which an incorrect state assumption can be exploited.

AC-3 Access Enforcement partial match

Enforces access decisions that depend on correctly maintained internal state, making incorrect operations due to state confusion less likely to succeed.

SA-17 Developer Security and Privacy Architecture and Design partial match

Requires developers to produce security architecture and design artifacts that must address correct internal state management.

SA-8 Security and Privacy Engineering Principles partial match

Mandates application of engineering principles (e.g., explicit state-machine design, fail-safe defaults) that stop incomplete state distinction from being introduced.

SC-23 Session Authenticity partial match

Requires protection of session state authenticity, directly reducing the chance that the system misidentifies its own session state.

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.PS-06 mostly match
prevents

Secure SDLC activities directly address proper state-machine design and testing that prevent incomplete state distinction.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities can surface this class of state-management flaw during assessments.

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.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect state-machine flaws that manifest as incomplete internal state distinction.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle practices can include state-machine validation and invariant checks that reduce incomplete internal state errors.

A.8.26 Application security requirements partial match
prevents

Explicit application security requirements can mandate state-transition validation and error-state handling.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage explicit state modelling and fail-safe transitions.

A.8.28 Secure coding partial match
prevents

Secure coding standards can require defensive checks against invalid or ambiguous internal states.

A.8.32 Change management partial match
prevents

Change-management procedures may indirectly catch state-related defects during release reviews.

References