CC100 0751-9x01: Incorrect Permission Assignment for Critical Resource
CVE-2024-41974 is a high-severity incorrect permission assignment for critical resource vulnerability in CC100 0751-9x01 from WAGO, with a CVSS 3.1 base score of 7.1 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 CC100 0751-9x01 versions: 4.5.10 (FW27) and earlier; 04.03.03 (72) and earlier; 04.04.03 (70) 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.36% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of CC100 0751-9x01 you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| WAGO | CC100 0751-9x01 | 4.5.10 (FW27) and earlier; 04.03.03 (72) and earlier; 04.04.03 (70) and earlier | Not stated |
| WAGO | PFC100 G2 0750-811x-xxxx-xxxx | 4.5.10 (FW27) and earlier | Not stated |
| WAGO | PFC200 G2 750-821x-xxx-xxx | 4.5.10 (FW27) and earlier | Not stated |
| WAGO | TP600 0762-420x/8000-000x | 4.5.10 (FW27) and earlier | Not stated |
| WAGO | TP600 0762-430x/8000-000x | 4.5.10 (FW27) and earlier | Not stated |
| WAGO | TP600 0762-520x/8000-000x | 4.5.10 (FW27) and earlier | Not stated |
| WAGO | TP600 0762-530x/8000-000x | 4.5.10 (FW27) and earlier | Not stated |
| WAGO | TP600 0762-620x/8000-000x | 4.5.10 (FW27) and earlier | Not stated |
| WAGO | TP600 0762-630x/8000-000x | 4.5.10 (FW27) and earlier | Not stated |
| WAGO | Edge Controller 0752-8303/8000-0002 | 4.5.10 (FW27) and earlier | Not stated |
| WAGO | PFC200 G2 0750-821x/xxx-xxx | 04.04.03 (70) and earlier | Not 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
- NoneNo data is disclosed.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H. Scored by CNA (cert.vde.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.1 | High | CNA (cert.vde.com) |
| CVSS 3.1 | 7.1 | High | CISA (ADP) |
Official description
A low privileged remote attacker may modify the BACNet service properties due to incorrect permission assignment for critical resources which may lead to a DoS limited to BACNet communication.
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
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in CC100 0751-9x01
- 7.2 High severity
- 8.8 High severity
- 8.1 High severity
Recent Incorrect Permission Assignment for Critical Resource vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.1 High severity
- 7.5 High severity
Spotted an error? Tell us.