{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-27986 exists.","fix":"No fix has been published for CVE-2020-27986 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-27986 is a high-severity vulnerability in n/a, published on 28 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-27986 and fix it if it is affected.\n\nWhat it is: CVE-2020-27986 is a high-severity vulnerability in n/a, published on 28 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-27986 exists.\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-27986/ (Markdown: https://insights.sbomify.com/CVE-2020-27986/index.md)","id":"CVE-2020-27986","markdown":"https://insights.sbomify.com/CVE-2020-27986/index.md","name":"CVE-2020-27986","record":{"aliases":["GHSA-56fw-8mg6-5hvp"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SonarQube","requires_auth":"none","summary":"Remote attackers can discover cleartext SMTP, SVN, and GitLab credentials via the API settings endpoint in SonarQube.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sonarqube","vendor":"sonarsource"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"SonarQube 8.4.2.36762 allows remote attackers to discover cleartext SMTP, SVN, and GitLab credentials via the api/settings/values URI. NOTE: reportedly, the vendor's position for SMTP and SVN is \"it is the administrator's responsibility to configure it.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2020/CVE-2020-27986.yaml","stars":null,"title":"SonarQube - Authentication Bypass"}],"tier":"weaponised"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2020-27986","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-27988"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2020-27985"},"products":["n/a"],"published":"2020-10-28","related":[{"cvss_score":6.7,"headline":"SQL injection in n/a","id":"CVE-2024-47911","kev_date_added":null,"published":"2024-10-04"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-17579","kev_date_added":null,"published":"2019-10-14"},{"cvss_score":5.3,"headline":"Auth bypass in n/a","id":"CVE-2020-28002","kev_date_added":null,"published":"2020-10-30"},{"cvss_score":4.9,"headline":"SonarQube logs sensitive information","id":"CVE-2024-38460","kev_date_added":null,"published":"2024-06-16"},{"cvss_score":4.3,"headline":"Exposure of Sensitive Information to an Unauthorized Actor in SonarSource SonarQube API","id":"CVE-2018-19413","kev_date_added":null,"published":"2018-12-14"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Remote attackers can discover cleartext SMTP, SVN, and GitLab credentials via the API settings endpoint in SonarQube.","url":"https://insights.sbomify.com/CVE-2020-27986/"}