PHOENIX CONTACT: TC Router and TC Cloud Client multiple vulnerabilities
Multiple Vulnerabilities exist in components used by the aforementioned products. See CVE-Details for more information.
describes (3)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-9436US | high8.8 | — | ||
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… | ||||
| CVE-2020-9435US | high7.5OT elevated | — | ||
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… | ||||
| CVE-2017-16544US | high8.8 | — | ||
In the add_match function in libbb/lineedit.c in BusyBox through 1.27.2, the tab autocomplete feature of the shell, used to get a list of filenames in a directory, does not sanitiz… | ||||
references
External citations — patches, advisories, analysis.
remediations (3)
- Mitigation
The pre-installed generic X.509 certificate should be renewed or replaced by an individual certificate during initial configuration. For details on replacing this certificate please refer to the user manual on page 51 et seq. Press 'renew' to create a new self-signed device certificate or upload a user specific certificate with the upload dialog. To avoid the manual generation of an individual certificate, the devices will be shipped with individual certificates starting with a future release.
- Mitigation
The pre-installed generic X.509 certificate should be renewed or replaced by an individual certificate during initial configuration. For details on replacing this certificate please refer to the user manual on page 51 et seq. Press 'renew' to create a new self-signed device certificate or upload a user specific certificate with the upload dialog. To avoid the manual generation of an individual certificate, the devices will be shipped with individual certificates starting with a future release.
- Mitigation
The pre-installed generic X.509 certificate should be renewed or replaced by an individual certificate during initial configuration. For details on replacing this certificate please refer to the user manual on page 51 et seq. Press 'renew' to create a new self-signed device certificate or upload a user specific certificate with the upload dialog. To avoid the manual generation of an individual certificate, the devices will be shipped with individual certificates starting with a future release.
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan