CVE-2024-36539
Projectcontour Contour 1.28.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-36539 is a critical-severity Insecure Inherited Permissions (CWE-277) vulnerability in Projectcontour Contour. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked in the top 33% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-6 (Least Privilege) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-36539 is an insecure permissions vulnerability (CWE-277) affecting Contour version 1.28.3. The flaw stems from overly permissive access controls that expose a service account token, enabling unauthorized retrieval of sensitive data and subsequent privilege escalation. It carries a CVSS 3.1 base score of 9.8, reflecting network-exploitable conditions with no required authentication or user interaction.
An unauthenticated remote attacker can obtain the service account token and leverage it to access sensitive information or elevate privileges within the affected Contour deployment. The EPSS score stands at 0.1398 with no material change from its recorded peak. The provided references consist of disclosure Gists that do not detail patches or mitigation steps.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-36151
Vulnerability Data
Insecure permissions in contour v1.28.3 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 8 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Least privilege requires that only the minimal necessary permissions are granted, which structurally prevents the definition and inheritance of overly broad permissions.
Access enforcement directly stops insecure inherited permissions from being applied to new objects by requiring all access decisions to follow approved authorizations.
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.
Directly addresses defining and enforcing secure access permissions and least privilege, which prevents insecure inheritance.
Configuration management practices include establishing secure permission baselines that avoid insecure inheritance.
Secure SDLC practices would catch and prevent defining insecure inherited permissions during development.
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 may detect permission issues but does not prevent insecure inheritance by design.
Privileged access rights management can limit inheritance of excessive permissions but does not directly address insecure default permission inheritance.
Secure development lifecycle practices can include permission model reviews but do not guarantee secure inherited permissions.
Secure system architecture principles can incorporate least-privilege permission models but do not specifically mandate secure inheritance.
Secure coding standards can explicitly require setting restrictive permissions at object creation, directly mitigating insecure inheritance.
Information access restriction policies can reduce risk from inherited permissions but do not enforce secure permission inheritance at creation time.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows Server 2016 (2 rules)
- V-224974 Domain-created Active Directory Organizational Unit (OU) objects must have proper access control permissions. prevents CWE-277
- V-224972 Active Directory Group Policy objects must have proper access control permissions. prevents CWE-277
Windows Server 2019 (2 rules)
- V-205743 Windows Server 2019 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions. prevents CWE-277
- V-205741 Windows Server 2019 Active Directory Group Policy objects must have proper access control permissions. prevents CWE-277
Windows Server 2022 (1 rule)
- V-254395 Windows Server 2022 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions. prevents CWE-277