Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HCVSS 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-3891 is a high-severity Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367) vulnerability in Lapce. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-44519
Vulnerability Data
Race condition in Lapce v0.2.8 allows an attacker to elevate privileges on the system
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.4.2V17.2.6
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.
Timestamps meeting UTC or offset standards help identify TOCTOU issues through precise chronological reconstruction of check/use operations.
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.
Secure SDLC practices directly include coding standards and reviews that prevent TOCTOU race conditions.
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.28 mandates secure coding practices (threat modelling, secure coding standards, peer review, test-driven development) that can prevent some TOCTOU instances by mandating atomic operations and file locking, but the clause governs a fallible human practice and TOCTOU is notoriously hard to catch in code review, leaving a nameable remainder of instances that slip through.
A.8.29's programme covers manual code review (High for CWE-367), penetration testing/dynamic analysis (High), and automated static analysis (SOAR Partial), reaching the weakness through both SOURCE and RUNTIME; the remainder is the inherent difficulty of reliably triggering and observing race conditions during one cycle and the patterns automated tools miss.
A.8.8's reach is DISCLOSURE — it sees only instances carrying a vendor-published flaw. TOCTOU does surface as CVEs (five observed examples in the CWE entry), so the weakness is not invisible to the clause, but the disclosed share is a minority: most CWE-367 instances live in first-party code that never receives a CVE, and A.8.8's scanning/inventory programme has no view of those.