{"answers":{"affected":"2 open source packages ship an affected version, including io.quarkus:quarkus-project. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5720 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-5720 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5720 is a high-severity vulnerability in gradle-plugin, published on 15 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-5720 and fix it if it is affected.\n\nWhat it is: CVE-2023-5720 is a high-severity vulnerability in gradle-plugin, published on 15 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-5720 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.quarkus:quarkus-project (Maven): affected from 3.0.0.CR1 up to 3.5.1; no fix listed\n- io.quarkus:quarkus-project (Maven): affected from 3.0.0.CR1 up to 3.5.1; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-5720/ (Markdown: https://insights.sbomify.com/CVE-2023-5720/index.md)","id":"CVE-2023-5720","markdown":"https://insights.sbomify.com/CVE-2023-5720/index.md","name":"CVE-2023-5720","record":{"aliases":["GHSA-p62q-5483-h57v"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Quarkus Gradle plugin","requires_auth":"low_privilege","summary":"Attackers can access sensitive build system information from Quarkus applications due to unsanitized artifacts created by the Gradle plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"quarkus","vendor":"quarkus"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-526","name":"Cleartext Storage of Sensitive Information in an Environment Variable"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Quarkus: build env information disclosure via gradle plugin","id":"CVE-2023-5720","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"Security feature bypass in Firefox","id":"CVE-2023-5721"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["3.0.0.CR1"],"last_affected":["3.5.1"],"package":"io.quarkus:quarkus-project","purl":null,"source":"GHSA-p62q-5483-h57v"},{"ecosystem":"Maven","fixed":[],"introduced":["3.0.0.CR1"],"last_affected":["3.5.1"],"package":"io.quarkus:quarkus-project","purl":"pkg:maven/io.quarkus/quarkus-project","source":"GHSA-p62q-5483-h57v"}],"prev":{"headline":"Red Lion Crimson Improper Neutralization of Null Byte or NUL Character","id":"CVE-2023-5719"},"products":["gradle-plugin"],"published":"2023-11-15","related":[{"cvss_score":9.8,"headline":"Code injection in quarkus dev ui config editor","id":"CVE-2022-4116","kev_date_added":null,"published":"2022-11-22"},{"cvss_score":9.8,"headline":"Quarkus does not terminate HTTP requests header context","id":"CVE-2022-2466","kev_date_added":null,"published":"2022-08-31"},{"cvss_score":9.1,"headline":"Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass","id":"CVE-2024-12225","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":8.8,"headline":"Quarkus authorization bypass via semicolon path normalization inconsistency","id":"CVE-2026-39852","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.8,"headline":"Privilege escalation in quarkus","id":"CVE-2022-0981","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":8.6,"headline":"Quarkus: json payload getting processed prior to security checks when rest resources are used with annotations.","id":"CVE-2023-6267","kev_date_added":null,"published":"2024-01-25"},{"cvss_score":8.1,"headline":"Quarkus: http security policy bypass","id":"CVE-2023-4853","kev_date_added":null,"published":"2023-09-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"Attackers can access sensitive build system information from Quarkus applications due to unsanitized artifacts created by the Gradle plugin.","url":"https://insights.sbomify.com/CVE-2023-5720/"}