CVE-2023-1976
Answer ≤ 1.0.6
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-1976 is a high-severity Password Aging with Long Expiration (CWE-263) vulnerability in Answer Answer. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 48th 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-1333
Vulnerability Data
Password Aging with Long Expiration in GitHub repository answerdev/answer prior to 1.0.6.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.4.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.
Credential management includes setting and enforcing password lifetime rules.
Password policy enforcement can directly specify maximum password age.
Hardened baselines commonly embed password-aging configuration settings.
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.
Requires policies for managing authentication credentials including password lifetime.
A.8.26 only requires that password aging requirements be identified and specified during development or acquisition; it never mandates, designs, or applies a short expiration period that would make the long-expiration flaw stop being present in the delivered product
A.8.27 mandates establishing and applying secure engineering principles (including least privilege, security by design, hardening) during the SDLC; it does not mandate or perform the concrete removal of an already-written long password-expiration value from product code
Mandates secure authentication mechanisms that include appropriate password expiration settings.