CVE-2023-49238
First published: Tue Jan 09 2024(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Gradle Enterprise | <2023.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2023-49238?
The severity of CVE-2023-49238 is considered to be high due to its potential for unauthorized access.
How do I fix CVE-2023-49238?
To fix CVE-2023-49238, ensure that the default initial system user password is changed immediately upon installation.
What software versions are affected by CVE-2023-49238?
CVE-2023-49238 affects Gradle Enterprise versions prior to 2023.1.
Can CVE-2023-49238 be exploited remotely?
Yes, CVE-2023-49238 can be exploited remotely by an attacker if they gain access before the initial password is changed.
Is there a workaround for CVE-2023-49238?
The primary workaround for CVE-2023-49238 is to configure the system securely and enforce password changes immediately after installation.
- agent/type
- agent/first-publish-date
- agent/author
- agent/weakness
- agent/severity
- agent/event
- agent/softwarecombine
- agent/references
- agent/tags
- agent/description
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- vendor/gradle
- canonical/gradle enterprise