First published: Mon Oct 23 2023(Updated: )
A flaw was found in Quarkus, where it does not properly sanitize artifacts created using the Gradle plugin, allowing certain build system information to remain. This flaw allows an attacker to access potentially sensitive information from the build system within the application.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/io.quarkus:quarkus-project | >=3.0.0.CR1<=3.5.1 | |
Quarkus Quarkus | >=3.0.1 | |
Quarkus Quarkus | =3.0.0-candidate_release1 | |
Quarkus Quarkus | =3.0.0-candidate_release2 | |
Quarkus Quarkus | >=3.0.1<3.2.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-5720 is a vulnerability that allows an attacker to access potentially sensitive information from the build system within the Quarkus application.
CVE-2023-5720 has a severity rating of 7.7, which is considered high.
CVE-2023-5720 affects Quarkus versions ranging from 3.0.0.CR1 to 3.5.1
To fix CVE-2023-5720, it is recommended to update Quarkus to a version that is not affected by the vulnerability.
More information about CVE-2023-5720 can be found at the following references: [Link 1](https://access.redhat.com/security/cve/CVE-2023-5720), [Link 2](https://bugzilla.redhat.com/show_bug.cgi?id=2245700), and [Link 3](https://nvd.nist.gov/vuln/detail/CVE-2023-5720).