CyberSecBulletin
CVE-2023-49238NVD status: Modified

Enterprise: Weak Password Requirements

CVE-2023-49238 is a critical-severity weak password requirements 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. The record lists version 2023.1 as the first without the flaw, so updating Enterprise to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.77% chance of exploitation within 30 days, higher than 56% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Enterprise to 2023.1 or a later version.
  2. Read the advisory on security.gradle.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
GradleEnterprisebefore 2023.12023.1

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 systemScoreSeverityScored by
CVSS 3.19.8CriticalNVD
CVSS 3.19.8CriticalCISA (ADP)

Official description

In Gradle Enterprise before 2023.1, a remote attacker may be able to gain access to a new installation (in certain installation scenarios) because of a non-unique initial system user password. Although this password must be changed upon the first login, it is possible that an attacker logs in before the legitimate administrator logs in.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Weak Password Requirements

The product does not require that users should have strong passwords.

How developers prevent this class of flaw

  • Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. See CWE-308 for further information.
  • Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.

More Weak Password Requirements vulnerabilities (CWE-521)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Enterprise

All Enterprise vulnerabilities

Recent Weak Password Requirements vulnerabilities

Spotted an error? Tell us.