CVE-2023-48387
Twca Jcicsecuritytool 4.2.3.32
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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-48387 is a high-severity Improper Verification of Source of a Communication Channel (CWE-940) vulnerability in Twca Jcicsecuritytool. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique LSASS Memory (T1003.001); ranked in the top 37% 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-52439
Vulnerability Data
TAIWAN-CA(TWCA) JCICSecurityTool fails to check the source website and access locations when executing multiple Registry-related functions. In the scenario where a user is using the JCICSecurityTool and has completed identity verification, if the user browses a malicious webpage created by…
more
an attacker, the attacker can exploit this vulnerability to read or modify any registry file under HKEY_CURRENT_USER, thereby achieving remote code execution.
- 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
Likely Mitigating Controls AI
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.
Enforces verification of the source of a communication channel by requiring identification and authentication of services first.
Requires explicit verification of the source and integrity of the channel used for authentication and other security functions.
Provides the means to verify the source of name-resolution responses instead of relying on unauthenticated channels.
Requires explicit verification of the communication source, blocking session hijacking via spoofed or alternate channels.
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