CVE-2023-7004
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-7004 is a medium-severity Improper Verification of Source of a Communication Channel (CWE-940) vulnerability in Alephsecurity (inferred from references). Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique LSASS Memory (T1003.001); ranked at the 5th 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 AC-17 (Remote Access) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-59196
Vulnerability Data
The TTLock App does not employ proper verification procedures to ensure that it is communicating with the expected device, allowing for connection to a device that spoofs the MAC address of a lock, which compromises the legitimate locks integrity.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.5.3V10.6.2V15.2.4
Mitigating Controls (NIST 800-53 r5) AI
IA-3 requires unique identification and authentication of devices before any communication channel is established, directly stopping acceptance of unverified origins.
AC-17 mandates documented restrictions and authentication requirements for remote access, blocking channels whose origins are not properly verified.
SC-23 protects session authenticity, ensuring the source of an established communication channel is verified and cannot be spoofed.
SC-7 enforces monitoring and control at external and key internal interfaces, preventing channels from unverified sources via boundary rules.
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.
Authentication of users/services/hardware directly enforces source verification for communication channels.
Verifying identity assertions prevents spoofed channel origins but does not cover all channel-establishment scenarios.
Network protections reduce unauthorized channel usage but do not specifically require origin verification at channel setup.
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.
Network security controls enforce source verification and channel authentication for incoming communications.
Security of network services includes validating the origin of service requests and connections.
A.8.24 mandates proper use of cryptography (algorithms, key management, protection of data in transit/storage) but has no bearing on whether a product correctly verifies the origin of an incoming communication channel; the weakness can still be present and exploited regardless of cryptographic controls.
A.8.26 requires identifying and specifying requirements for resilience against malicious attacks (explicitly naming SQL injection) plus input validation, authentication, segregation of access, output controls, and cryptography; these can address origin verification for expected channels in some (but not all) application designs, leaving a bounded remainder where the weakness is still exploitable.
Secure coding practices can prevent improper source verification if explicitly required.
A.8.5 chooses and strengthens authentication techniques for claimed identities at log-on; it has no bearing on whether an established channel's origin is verified after the fact, so the weakness can still be exploited