CVE-2022-30587

7.5 HIGH

📋 TL;DR

Gradle Enterprise versions through 2022.2.2 have an incorrect access control vulnerability that allows unauthorized users to access sensitive information. This affects organizations using Gradle Enterprise for build automation and software development. The vulnerability stems from improper authorization checks in certain endpoints.

💻 Affected Systems

Products:
  • Gradle Enterprise
Versions: All versions through 2022.2.2
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments of affected versions are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could access sensitive build artifacts, source code, credentials, and proprietary intellectual property stored in Gradle Enterprise.

🟠

Likely Case

Unauthorized access to build logs, dependency information, and potentially sensitive configuration data.

🟢

If Mitigated

Limited exposure if network segmentation restricts access and proper authentication is enforced.

🌐 Internet-Facing: HIGH if Gradle Enterprise is exposed to the internet without proper access controls.
🏢 Internal Only: MEDIUM as internal attackers could still exploit the vulnerability to access sensitive build information.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires network access to Gradle Enterprise but does not require authentication. The vulnerability is in authorization logic, not authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2022.2.3 and later

Vendor Advisory: https://security.gradle.com/advisory/2022-10

Restart Required: Yes

Instructions:

1. Backup your Gradle Enterprise instance. 2. Upgrade to version 2022.2.3 or later. 3. Restart the Gradle Enterprise service. 4. Verify the upgrade was successful.

🔧 Temporary Workarounds

Network Access Restriction

all

Restrict network access to Gradle Enterprise to only trusted IP addresses and networks.

# Use firewall rules to restrict access
# Example: iptables -A INPUT -p tcp --dport 443 -s trusted_network -j ACCEPT
# Example: iptables -A INPUT -p tcp --dport 443 -j DROP

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate Gradle Enterprise from untrusted networks
  • Enable comprehensive logging and monitoring for unauthorized access attempts

🔍 How to Verify

Check if Vulnerable:

Check Gradle Enterprise version in administration console or via API. If version is 2022.2.2 or earlier, it is vulnerable.

Check Version:

curl -k https://gradle-enterprise-host/api/version

Verify Fix Applied:

Verify version is 2022.2.3 or later in administration console and test that unauthorized access to sensitive endpoints is properly blocked.

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to sensitive endpoints
  • Access to /api/* endpoints from unauthorized users
  • Failed authorization logs for previously accessible endpoints

Network Indicators:

  • Unusual access patterns to Gradle Enterprise from unexpected IP addresses
  • Traffic to sensitive API endpoints without proper authentication headers

SIEM Query:

source="gradle-enterprise" AND (event_type="access_denied" OR status_code=403) AND uri_path="/api/*"

🔗 References

📤 Share & Export