Enterprise: Incorrect Default Permissions
CVE-2022-27919 is a critical-severity incorrect default permissions vulnerability in Enterprise from Gradle, 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 Enterprise versions: 2020.4 through 2021.4.3. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.84% chance of exploitation within 30 days, higher than 79% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of Enterprise you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on security.gradle.com for workarounds and exact fixed builds.
- 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 |
|---|---|---|---|
| Gradle | Enterprise | 2020.4 through 2021.4.3 | Not stated |
Version data comes from NVD's product matching. 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 NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 2.0 | 7.5 | High | NVD |
Official description
Gradle Enterprise before 2022.1 allows remote code execution if the installation process did not specify an initial configuration file. The configuration allows certain anonymous access to administration and an API.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Default Permissions
During installation, installed file permissions are set to allow anyone to modify those files.
How developers prevent this class of flaw
- The architecture needs to access and modification attributes for files to only those users who actually require those actions.
- 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 Incorrect Default Permissions vulnerabilities (CWE-276)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
- security.gradle.com/advisory/2022-05Mitigation
Other vulnerabilities in Enterprise
- 7.1 High severity
- 8.3 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
Recent Incorrect Default Permissions vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.