CVE-2023-3520
It-Novum Openitcockpit ≤ 4.6.6
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/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-3520 is a medium-severity Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (CWE-614) vulnerability in It-Novum Openitcockpit. Its CVSS base score is 4.6 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique LSASS Memory (T1003.001); ranked at the 21th 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-44177
Vulnerability Data
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in GitHub repository it-novum/openitcockpit prior to 4.6.6.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.1
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.
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.
Setting the Secure attribute is a direct mechanism for protecting sensitive session data in transit over HTTPS.
Enforcing hardened configuration baselines includes requiring the Secure flag on sensitive cookies.
Secure SDLC practices explicitly require correct use of security attributes such as the cookie Secure flag.
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.
A.8.26 only requires that security requirements (including those that could address cookie flags via 8.24 cryptography or other guidance) be identified and specified during development; it does not itself enforce, implement, or stop exploitation of the missing Secure attribute.
Secure coding practices directly prevent missing the Secure attribute on sensitive cookies, though the control covers many other coding issues.
Secure authentication control requires protection of session credentials, directly addressed by setting the Secure flag on sensitive cookies.