{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-49238 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-49238 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-49238 is a critical vulnerability in n/a, published on 9 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-49238 and fix it if it is affected.\n\nWhat it is: CVE-2023-49238 is a critical vulnerability in n/a, published on 9 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-49238 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-49238/ (Markdown: https://insights.sbomify.com/CVE-2023-49238/index.md)","id":"CVE-2023-49238","markdown":"https://insights.sbomify.com/CVE-2023-49238/index.md","name":"CVE-2023-49238","record":{"aliases":["GHSA-4766-3xqh-rp5x"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Gradle Enterprise","requires_auth":"none","summary":"Remote attackers can gain unauthorized access to new Gradle Enterprise installations by exploiting non-unique initial system user passwords before the administrator logs in.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"enterprise","vendor":"gradle"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-521","name":"Weak Password Requirements"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-49238","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in EMUI","id":"CVE-2023-49239"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2023-49237"},"products":["n/a"],"published":"2024-01-09","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2022-27919","kev_date_added":null,"published":"2022-03-25"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2019-11402","kev_date_added":null,"published":"2019-04-21"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-15776","kev_date_added":null,"published":"2020-09-18"},{"cvss_score":8.1,"headline":"Misconfiguration in n/a","id":"CVE-2022-25364","kev_date_added":null,"published":"2022-03-17"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2022-41575","kev_date_added":null,"published":"2022-10-21"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2022-41574","kev_date_added":null,"published":"2022-10-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["n/a"]},"summary":"Remote attackers can gain unauthorized access to new Gradle Enterprise installations by exploiting non-unique initial system user passwords before the administrator logs in.","url":"https://insights.sbomify.com/CVE-2023-49238/"}