{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15772 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15772 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15772 is a medium-severity vulnerability in n/a, published on 18 Sep 2020. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15772 and fix it if it is affected.\n\nWhat it is: CVE-2020-15772 is a medium-severity vulnerability in n/a, published on 18 Sep 2020. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-15772 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-2020-15772/ (Markdown: https://insights.sbomify.com/CVE-2020-15772/index.md)","id":"CVE-2020-15772","markdown":"https://insights.sbomify.com/CVE-2020-15772/index.md","name":"CVE-2020-15772","record":{"aliases":["GHSA-7cj4-x7wr-qf2p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Gradle Enterprise","requires_auth":"high_privilege","summary":"Administrators can trigger server-side request forgery via XML external entity injection in SAML metadata uploads, potentially exposing internal data.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"enterprise","vendor":"gradle"}],"cvss":{"score":4.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"An issue was discovered in Gradle Enterprise 2018.5 - 2020.2.4. When configuring Gradle Enterprise to integrate with a SAML identity provider, an XML metadata file can be uploaded by an administrator. The server side processing of this file dereferences XML External Entities (XXE), allowing a remote attacker with administrative access to perform server side request forgery.","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":"XML external entity in n/a","id":"CVE-2020-15772","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xxe","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-15773"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-15771"},"products":["n/a"],"published":"2020-09-18","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-49238","kev_date_added":null,"published":"2024-01-09"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Administrators can trigger server-side request forgery via XML external entity injection in SAML metadata uploads, potentially exposing internal data.","url":"https://insights.sbomify.com/CVE-2020-15772/"}