CyberSecBulletin
CVE-2023-46142NVD status: Modified

AXC F 1152: Incorrect Permission Assignment for Critical Resource

Published Updated By the CyberSecBulletin desk

CVE-2023-46142 is a high-severity incorrect permission assignment for critical resource vulnerability in AXC F 1152 from Phoenix Contact, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected AXC F 1152 versions: 2024.0 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.74% chance of exploitation within 30 days, higher than 55% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of AXC F 1152 you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
PHOENIX CONTACTAXC F 11522024.0 and earlierNot stated
PHOENIX CONTACTAXC F 21522024.0 and earlierNot stated
PHOENIX CONTACTAXC F 31522024.0 and earlierNot stated
PHOENIX CONTACTBPC 9102S2024.0 and earlierNot stated
PHOENIX CONTACTEPC 15022024.0 and earlierNot stated
PHOENIX CONTACTEPC 15222024.0 and earlierNot stated
PHOENIX CONTACTPLCnext Engineer2024.0 and earlierNot stated
PHOENIX CONTACTRFC 4072R2024.0 and earlierNot stated
PHOENIX CONTACTRFC 4072S2024.0 and earlierNot stated
PhoenixcontactAxc F 1152 Firmware2024.0 and earlierNot stated
PhoenixcontactAxc F 2152 Firmware2024.0 and earlierNot stated
PhoenixcontactAxc F 3152 Firmware2024.0 and earlierNot stated
PhoenixcontactBpc 9102s Firmware2024.0 and earlierNot stated
PhoenixcontactEpc 1502 Firmware2024.0 and earlierNot stated
PhoenixcontactEpc 1522 Firmware2024.0 and earlierNot stated
PhoenixcontactRfc 4072r Firmware2024.0 and earlierNot stated
PhoenixcontactRfc 4072s Firmware2024.0 and earlierNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (cert.vde.com).

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Permission Assignment for Critical Resource

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

How developers prevent this class of flaw

  • When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
  • Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
  • During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.

More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

Other vulnerabilities in AXC F 1152

All AXC F 1152 vulnerabilities

Recent Incorrect Permission Assignment for Critical Resource vulnerabilities

Spotted an error? Tell us.