CVE-2024-0349
Engineers Online Portal Project Engineers Online Portal 1.0
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2024-0349 is a low-severity Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (CWE-614) vulnerability in Engineers Online Portal Project Engineers Online Portal. Its CVSS base score is 3.7 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steal Web Session Cookie (T1539); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-16145
Vulnerability Data
A vulnerability was found in SourceCodester Engineers Online Portal 1.0. It has been declared as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to sensitive cookie without secure attribute. The attack can be launched remotely. The…
more
complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier VDB-250117 was assigned to this vulnerability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.1
Mitigating Controls (NIST 800-53 r5) AI
Requiring confidentiality protection for transmitted information forces use of HTTPS-only cookies via the Secure attribute, eliminating exposure of sensitive session data.
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.
Use of cryptography control mandates encryption in transit, which HTTPS provides, but does not specifically require the Secure cookie attribute.
Application security requirements can include cookie security settings, but the control is broader and does not explicitly mandate the 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.