CVE-2023-46142
highpriority · track · 0EPSS 0.007 · 55 %ileDEEUUSEPSS · scored 2026-10-27
A incorrect permission assignment for critical resource vulnerability in PLCnext products allows an remote attacker with low privileges to gain full access on the affected devices.
remediations
Vendor fix, mitigation, or workaround guidance, as published by each source.
A vendor fix is available.
- Fixedphoenix_contact_psirt
PLCnext Control security feature set and hardening are continuously improved. Please check the PLCnext Control product download pages for updated versions and the PSIRT webpage https://phoenixcontact.com/psirt for updated information's and firmware regularly. We recommend that our customers always use the latest LTS versions, as known security vulnerabilities are regularly fixed. The latest version at the time of publication of this advisory is 2023.0.7 LTS Hotfix.
- Mitigationphoenix_contact_psirt
PLCnext Control is developed and designed for use in protected industrial networks. In this approach, the production plant is protected against attacks, especially from the outside, by a multi-level perimeter, including firewalls, and by dividing the plant into OT zones using firewalls. This concept is supported by organizational measures in the production facility as part of a security management system. To achieve security, measures are required at all levels. It must be ensured that the application is always transferred or stored in protected environments. This applies to both data in transmission and data at rest. Connections between the engineering tools (PLCnext Engineer) and PLCnext Control must always be in a locally protected environment or, in the case of remote access, protected by VPN. Project data should not be sent as a file via email or other transmission mechanisms without additional integrity and authenticity checks. Project data should only be stored in protected environments. For general information and recommendations on security measures to protect network-enabled devices, refer to the application note: Application note Security PLCnext Control provides a feature set that supports users in setting up a separated protected environment, for example, by using separated Ethernet ports, firewalls, user and certificate management and integrity checks. These features can reduce the attack surface of this vulnerability. For more information's refer to the PLCnext Info Centers. Concepts how to use PLCnext Control to establish protected industrial networks are described in the Security Context description Generic security concept.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (36)
Products and version ranges known to be affected.
- phoenixcontact axc f 1152 firmware≤ 2024.0nvdUScpe:2.3:o:phoenixcontact:axc_f_1152_firmware:*:*:*:*:*:*:*:*
- phoenixcontact axc f 2152 firmware≤ 2024.0nvdUScpe:2.3:o:phoenixcontact:axc_f_2152_firmware:*:*:*:*:*:*:*:*
- phoenixcontact axc f 3152 firmware≤ 2024.0nvdUScpe:2.3:o:phoenixcontact:axc_f_3152_firmware:*:*:*:*:*:*:*:*
- phoenixcontact bpc 9102s firmware≤ 2024.0nvdUScpe:2.3:o:phoenixcontact:bpc_9102s_firmware:*:*:*:*:*:*:*:*
- phoenixcontact epc 1502 firmware≤ 2024.0nvdUScpe:2.3:o:phoenixcontact:epc_1502_firmware:*:*:*:*:*:*:*:*
- phoenixcontact epc 1522 firmware≤ 2024.0nvdUScpe:2.3:o:phoenixcontact:epc_1522_firmware:*:*:*:*:*:*:*:*
- phoenixcontact plcnext engineer≤ 2024.0nvdUScpe:2.3:a:phoenixcontact:plcnext_engineer:*:*:*:*:*:*:*:*
- phoenixcontact rfc 4072r firmware≤ 2024.0nvdUScpe:2.3:o:phoenixcontact:rfc_4072r_firmware:*:*:*:*:*:*:*:*
- phoenixcontact rfc 4072s firmware≤ 2024.0nvdUScpe:2.3:o:phoenixcontact:rfc_4072s_firmware:*:*:*:*:*:*:*:*
advisories (1)
Vendor and ecosystem advisories describing this.
- VDE-2023-056Phoenix Contact: PLCnext prone to Incorrect Permission Assignment for Critical Resource2023-12-12csaf · phoenix_contact_psirtDE
PLCnext Control provides authentication and integrity check for the application.An authenticated, skilled attacker might be able to manipulate the application (e.g.: logic files, executable logic, configurations) in a special crafted way that the integrity check will not be able to recognize these tampering attempts which are then difficult to remove. To successfully exploit this vulnerability, the attacker must have access to the application either with PLCnext Engineer on the Engineering station, the stored application, the application during download or the application storage on the PLC.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (5)
External citations — patches, advisories, analysis.
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan