external-secrets: Insecure Inherited Permissions
CVE-2024-36540 is a critical-severity insecure inherited permissions vulnerability in external-secrets, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected external-secrets versions: 0.9.16. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.42% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of external-secrets you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| External-secrets | external-secrets | 0.9.16 | Not stated |
| External-secrets | External Secrets Operator | 0.9.16 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
Insecure permissions in external-secrets v0.9.16 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insecure Inherited Permissions
A product defines a set of insecure permissions that are inherited by objects that are created by the program.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
More Insecure Inherited Permissions vulnerabilities (CWE-277)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- gist.github.com/HouqiyuA/a4834f3c8450f9d89e2bc4d5c4beef6aThird Party Advisory
Other vulnerabilities in external-secrets
- 7.1 High severity
- 8.8 High severity
- 8.7 High severity
- 7.1 High severity
- 8.8 High severity
Recent Insecure Inherited Permissions vulnerabilities
- 8.4 High severity
- 7.5 High severity
- 7.8 High severity
- 7.1 High severity
- 8.4 High severity
- 7.8 High severity
Spotted an error? Tell us.