CVE-2023-42446
Powauth Pow 1.0.14 – 1.0.34
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NSummary
CVE-2023-42446 is a medium-severity Improper Validation of Certificate Expiration (CWE-298) vulnerability in Powauth Pow. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Subvert Trust Controls (T1553); ranked at the 37th percentile by exploit likelihood (below the median); 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-2404
Vulnerability Data
Pow is a authentication and user management solution for Phoenix and Plug-based apps. Starting in version 1.0.14 and prior to version 1.0.34, use of `Pow.Store.Backend.MnesiaCache` is susceptible to session hijacking as expired keys are not being invalidated correctly on startup.…
more
A session may expire when all `Pow.Store.Backend.MnesiaCache` instances have been shut down for a period that is longer than a session's remaining TTL. Version 1.0.34 contains a patch for this issue. As a workaround, expired keys, including all expired sessions, can be manually invalidated.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 2 OS baselines
—
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.
Enforcing managed authorizations and revocations directly prevents post-release operations on credentials or entitlements.
Secure development practices eliminate the root coding flaw that permits use-after-release.
Proper authentication of services/hardware requires certificate validation including expiration checks.
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.
Security testing can detect missing certificate expiration checks but does not constitute the control's full intent.
Enforces timely deletion of resources so they cannot be used after release.
Cryptography policy requires proper certificate lifecycle management including expiration validation.
Secure coding practices can include certificate validation checks but do not address the control's broader scope.
Change-management processes can introduce or remove resource-lifetime controls.
Secure authentication mandates validation of certificate attributes such as expiration dates.