{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25620 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-25620 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-25620 is a high-severity vulnerability in n/a, published on 16 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-25620 and fix it if it is affected.\n\nWhat it is: CVE-2020-25620 is a high-severity vulnerability in n/a, published on 16 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-25620 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-25620/ (Markdown: https://insights.sbomify.com/CVE-2020-25620/index.md)","id":"CVE-2020-25620","markdown":"https://insights.sbomify.com/CVE-2020-25620/index.md","name":"CVE-2020-25620","record":{"aliases":["GHSA-6v6x-q433-6x54"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SolarWinds N-Central","requires_auth":"low_privilege","summary":"Hard-coded credentials in SolarWinds N-Central allow attackers to log in to the administrative console and web interface.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"n-central","vendor":"solarwinds"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered in SolarWinds N-Central 12.3.0.670. Hard-coded Credentials exist by default for local user accounts named support@n-able.com and nableadmin@n-able.com. These allow logins to the N-Central Administrative Console (NAC) and/or the regular web interface.","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-2020-25620","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-25621"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-25619"},"products":["n/a"],"published":"2020-12-16","related":[{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2020-25617","kev_date_added":null,"published":"2020-12-16"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-25618","kev_date_added":null,"published":"2020-12-16"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-25622","kev_date_added":null,"published":"2020-12-16"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2020-15909","kev_date_added":null,"published":"2020-10-19"},{"cvss_score":8.4,"headline":"Missing authorization in n/a","id":"CVE-2020-25621","kev_date_added":null,"published":"2020-12-16"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-7984","kev_date_added":null,"published":"2020-01-26"}],"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":"Hard-coded credentials in SolarWinds N-Central allow attackers to log in to the administrative console and web interface.","url":"https://insights.sbomify.com/CVE-2020-25620/"}