CVE-2023-3050
Tmtmakine Lockcell Firmware ≤ 15.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-3050 is a critical-severity Reliance on Cookies without Validation and Integrity Checking in a Security Decision (CWE-784) vulnerability in Tmtmakine Lockcell Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 30% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-43742
Vulnerability Data
Reliance on Cookies without Validation and Integrity Checking in a Security Decision vulnerability in TMT Lockcell allows Privilege Abuse, Authentication Bypass. This issue affects Lockcell: before 15.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.1
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.
Strong authentication policies and mechanisms directly prevent reliance on unvalidated cookies for identity decisions.
Verifying identity assertions explicitly requires integrity and validity checks that eliminate untrusted cookie usage.
Enforcing authorization policies ensures access decisions are not based solely on unvalidated client-side cookies.
Integrity protections for data-at-rest can apply to cookie stores but do not cover validation during use.
Integrity protection for data-in-transit can help safeguard cookie values but does not address server-side validation logic.
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.26 requires identifying and specifying requirements (including resilience against SQLi, input validation, access segregation, and cryptography per 8.24) that can address cookie-based security decisions, but this is only a minority slice of the weakness class as it depends on downstream implementation of those requirements rather than directly preventing exploitation.
Secure coding practices require integrity checks on security-critical cookies used for decisions.
Security testing can detect missing cookie validation but does not prevent the weakness by itself.
Information access restriction requires proper validation of identity tokens before granting access.