NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
154 matching advisories · page 4 of 6Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.8 CVE-2021-34582 In Phoenix Contact FL MGUARD 1102 and 1105 in Versions 1.4.0, 1.4.1 and 1.5.0 a user with high privileges can inject HTML code (XSS) through web-based manageme… phoenixcontact · fl_mguard_1102_firmware, phoenixcontact · fl_mguard_1105_firmware 2021-11-10 high7.8 CVE-2021-34597 Improper Input Validation vulnerability in PC Worx Automation Suite of Phoenix Contact up to version 1.88 could allow an attacker with a manipulated project fi… phoenixcontact · pc_worx, phoenixcontact · pc_worx_express 2021-11-04 high7.5 CVE-2021-34570 Multiple Phoenix Contact PLCnext control devices in versions prior to 2021.0.5 LTS are prone to a DoS attack through special crafted JSON requests. phoenixcontact · plcnext_technology_starterkit_firmware, phoenixcontact · axc_f_2152_starterkit_firmware, phoenixcontact · rfc_4072s_firmware +3 2021-09-27 high7.8 CVE-2021-33542 Phoenix Contact Classic Automation Worx Software Suite in Version 1.87 and below is affected by a remote code execution vulnerability. phoenixcontact · config\+, phoenixcontact · pc_worx, phoenixcontact · pc_worx_express 2021-06-25 high7.5 CVE-2021-33541 Phoenix Contact Classic Line Controllers ILC1x0 and ILC1x1 in all versions/variants are affected by a Denial-of-Service vulnerability. phoenixcontact · ilc1x0_firmware, phoenixcontact · ilc1x1_firmware 2021-06-25 high7.3 CVE-2021-33540 In certain devices of the Phoenix Contact AXL F BK and IL BK product families an undocumented password protected FTP access to the root directory exists. phoenixcontact · axl_f_bk_pn_tps_xc_firmware, phoenixcontact · axl_f_bk_pn_tps_firmware, phoenixcontact · axl_f_bk_eip_firmware +9 2021-06-25 high7.5 CVE-2021-21005 In Phoenix Contact FL SWITCH SMCS series products in multiple versions if an attacker sends a hand-crafted TCP-Packet with the Urgent-Flag set and the Urgent-P… phoenixcontact · fl_switch_smcs_16tx_firmware, phoenixcontact · fl_switch_smcs_14tx\/2fx_firmware, phoenixcontact · fl_switch_smcs_14tx\/2fx-sm_firmware +9 2021-06-25 high7.4 CVE-2021-21004 In Phoenix Contact FL SWITCH SMCS series products in multiple versions an attacker may insert malicious code via LLDP frames into the web-based management whic… phoenixcontact · fl_switch_smcs_16tx_firmware, phoenixcontact · fl_switch_smcs_14tx\/2fx_firmware, phoenixcontact · fl_switch_smcs_14tx\/2fx-sm_firmware +9 2021-06-25 medium5.3 CVE-2021-21003 In Phoenix Contact FL SWITCH SMCS series products in multiple versions fragmented TCP-Packets may cause a Denial of Service of Web-, SNMP- and ICMP-Echo servic… phoenixcontact · fl_switch_smcs_16tx_firmware, phoenixcontact · fl_switch_smcs_14tx\/2fx_firmware, phoenixcontact · fl_switch_smcs_14tx\/2fx-sm_firmware +9 2021-06-25 high7.5 CVE-2021-21002 In Phoenix Contact FL COMSERVER UNI in versions < 2.40 a invalid Modbus exception response can lead to a temporary denial of service. phoenixcontact · fl_comserver_uni_232\/422\/485_firmware, phoenixcontact · fl_comserver_uni_232\/422\/485-t_firmware 2021-06-25 medium5.4 CVE-2020-12523 On Phoenix Contact mGuard Devices versions before 8.8.3 LAN ports get functional after reboot even if they are disabled in the device configuration. phoenixcontact · tc_mguard_rs4000_4g_vzw_vpn_firmware, phoenixcontact · tc_mguard_rs4000_4g_att_vpn_firmware, phoenixcontact · fl_mguard_rs4004_tx\/dtx_firmware +6 2020-12-17 medium6.5 CVE-2020-12521 On Phoenix Contact PLCnext Control Devices versions before 2021.0 LTS a specially crafted LLDP packet may lead to a high system load in the PROFINET stack. phoenixcontact · plcnext_firmware 2020-12-17 high8.8 CVE-2020-12519 On Phoenix Contact PLCnext Control Devices versions before 2021.0 LTS an attacker can use this vulnerability i.e. phoenixcontact · plcnext_firmware 2020-12-17 medium5.5 CVE-2020-12518 On Phoenix Contact PLCnext Control Devices versions before 2021.0 LTS an attacker can use the knowledge gained by reading the insufficiently protected sensitiv… phoenixcontact · plcnext_firmware 2020-12-17 high8.8 CVE-2020-12517 On Phoenix Contact PLCnext Control Devices versions before 2021.0 LTS an authenticated low privileged user could embed malicious Javascript code to gain admin … phoenixcontact · plcnext_firmware 2020-12-17 high7.5 CVE-2020-12524 Uncontrolled Resource Consumption can be exploited to cause the Phoenix Contact HMIs BTP 2043W, BTP 2070W and BTP 2102W in all versions to become unresponsive … phoenixcontact · btp_2043w_firmware, phoenixcontact · btp_2070w_firmware, phoenixcontact · btp_2102w_firmware 2020-12-02 high8.2 CVE-2020-12499 In PHOENIX CONTACT PLCnext Engineer version 2020.3.1 and earlier an improper path sanitation vulnerability exists on import of project files. phoenixcontact · plcnext_engineer 2020-07-21 high7.8 CVE-2020-12498 mwe file parsing in Phoenix Contact PC Worx and PC Worx Express version 1.87 and earlier is vulnerable to out-of-bounds read remote code execution. phoenixcontact · pc_worx, phoenixcontact · pc_worx_express 2020-07-01 high7.8 CVE-2020-12497 PLCopen XML file parsing in Phoenix Contact PC Worx and PC Worx Express version 1.87 and earlier can lead to a stack-based overflow. phoenixcontact · pc_worx, phoenixcontact · pc_worx_express 2020-07-01 high7.8 CVE-2020-10940 Local Privilege Escalation can occur in PHOENIX CONTACT PORTICO SERVER through 3.0.7 when installed to run as a service. phoenixcontact · portico_server_1_client, phoenixcontact · portico_server_16_client, phoenixcontact · portico_server_4_client 2020-03-27 high7.8 CVE-2020-10939 Insecure, default path permissions in PHOENIX CONTACT PC WORX SRT through 1.14 allow for local privilege escalation. phoenixcontact · pc_worx_srt 2020-03-27 high8.8 CVE-2020-9436 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.0… phoenixcontact · tc_router_3002t-4g_firmware, phoenixcontact · tc_router_2002t-3g_firmware, phoenixcontact · tc_router_3002t-4g_vzw_firmware +3 2020-03-12 high7.5 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-4G ATT through 2.0… phoenixcontact · tc_router_3002t-4g_firmware, phoenixcontact · tc_router_2002t-3g_firmware, phoenixcontact · tc_router_3002t-4g_vzw_firmware +3 2020-03-12 high7.5 CVE-2018-16994 An issue was discovered on PHOENIX CONTACT AXL F BK PN <=1.0.4, AXL F BK ETH <= 1.12, and AXL F BK ETH XC <= 1.11 devices and Bosch Rexroth S20-ETH-BK and Rexr… phoenixcontact · axl_f_bk_pn_firmware, phoenixcontact · axl_f_bk_eth_firmware, phoenixcontact · axl_f_bk_eth_xc_firmware 2020-02-18 high8.2 CVE-2019-18352 Improper access control exists on PHOENIX CONTACT FL NAT 2208 devices before V2.90 and FL NAT 2304-2GC-2SFP devices before V2.90 when using MAC-based port secu… phoenixcontact · fl_nat_2208_firmware, phoenixcontact · fl_nat_2304-2gc-2sfp_firmware 2020-02-18 critical9.4 CVE-2020-8768 An issue was discovered on Phoenix Contact Emalytics Controller ILC 2050 BI before 1.2.3 and BI-L before 1.2.3 devices. phoenixcontact · ilc_2050_bi_firmware, phoenixcontact · ilc_2050_bi-l_firmware 2020-02-17 high7.8 CVE-2019-16675 An issue was discovered in PHOENIX CONTACT PC Worx through 1.86, PC Worx Express through 1.86, and Config+ through 1.86. phoenixcontact · config\+, phoenixcontact · pc_worx, phoenixcontact · pc_worx_express 2019-10-31 high8.8 CVE-2019-12870 An issue was discovered in PHOENIX CONTACT PC Worx through 1.86, PC Worx Express through 1.86, and Config+ through 1.86. phoenixcontact · automationworx_software_suite 2019-06-24 high8.8 CVE-2019-12869 An issue was discovered in PHOENIX CONTACT PC Worx through 1.86, PC Worx Express through 1.86, and Config+ through 1.86. phoenixcontact · automationworx_software_suite 2019-06-24 high8.8 CVE-2019-12871 An issue was discovered in PHOENIX CONTACT PC Worx through 1.86, PC Worx Express through 1.86, and Config+ through 1.86. phoenixcontact · automationworx_software_suite 2019-06-24

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.