{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15767 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15767 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15767 is a medium-severity vulnerability in n/a, published on 18 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-15767 and fix it if it is affected.\n\nWhat it is: CVE-2020-15767 is a medium-severity vulnerability in n/a, published on 18 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-15767 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-15767/ (Markdown: https://insights.sbomify.com/CVE-2020-15767/index.md)","id":"CVE-2020-15767","markdown":"https://insights.sbomify.com/CVE-2020-15767/index.md","name":"CVE-2020-15767","record":{"aliases":["GHSA-w2c9-99w6-qcrh"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Gradle Enterprise","requires_auth":"none","summary":"Attackers can steal CSRF tokens via MITM if users access Gradle Enterprise over HTTP, enabling CSRF attacks.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"enterprise","vendor":"gradle"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"An issue was discovered in Gradle Enterprise before 2020.2.5. The cookie used to convey the CSRF prevention token is not annotated with the “secure” attribute, which allows an attacker with the ability to MITM plain HTTP requests to obtain it, if the user mistakenly uses a HTTP instead of HTTPS address to access the server. This cookie value could then be used to perform CSRF.","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":"Cross-site request forgery in n/a","id":"CVE-2020-15767","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-15768"},"packages":[],"prev":{"headline":"Unused CVE for 2020","id":"CVE-2020-15766"},"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":"Attackers can steal CSRF tokens via MITM if users access Gradle Enterprise over HTTP, enabling CSRF attacks.","url":"https://insights.sbomify.com/CVE-2020-15767/"}