{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20025 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20025 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20025 is a critical vulnerability in n/a, published on 29 Jul 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-2019-20025 and fix it if it is affected.\n\nWhat it is: CVE-2019-20025 is a critical vulnerability in n/a, published on 29 Jul 2020. 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-2019-20025 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-2019-20025/ (Markdown: https://insights.sbomify.com/CVE-2019-20025/index.md)","id":"CVE-2019-20025","markdown":"https://insights.sbomify.com/CVE-2019-20025/index.md","name":"CVE-2019-20025","record":{"aliases":["GHSA-7q4r-vh4x-gr7v"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"NEC SV9100 PBX","requires_auth":"none","summary":"Unauthenticated attackers can log in with hardcoded manufacturer credentials to gain full control of NEC SV9100 PBX devices.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sv9100_firmware","vendor":"nec"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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-798","name":"Use of Hard-coded Credentials"}],"description":"Certain builds of NEC SV9100 software could allow an unauthenticated, remote attacker to log into a device running an affected release with a hardcoded username and password, aka a Static Credential Vulnerability. The vulnerability is due to an undocumented user account with manufacturer privilege level. An attacker could exploit this vulnerability by using this account to remotely log into an affected device. A successful exploit could allow the attacker to log into the device with manufacturer level access. This vulnerability affects SV9100 PBXes that are running software release 6.0 or higher. This vulnerability does not affect SV9100 software releases prior to 6.0.","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-2019-20025","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2019-20026"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-20024"},"products":["n/a"],"published":"2020-07-29","related":[{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2019-20026","kev_date_added":null,"published":"2020-07-29"}],"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-05","vendors":["n/a"]},"summary":"Unauthenticated attackers can log in with hardcoded manufacturer credentials to gain full control of NEC SV9100 PBX devices.","url":"https://insights.sbomify.com/CVE-2019-20025/"}