CyberSecBulletin
CVE-2023-39257NVD status: Modified

Rugged Control Center (RCC): Improper Access Control

CVE-2023-39257 is a high-severity improper access control vulnerability in Rugged Control Center (RCC) from Dell, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Rugged Control Center (RCC) versions: Versions prior to 4.7. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.2% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Rugged Control Center to 4.7 or a later version.
  2. Read the advisory on dell.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
DellRugged Control Center (RCC)Versions prior to 4.7Not stated
DellRugged Control Centerbefore 4.74.7

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
LocalThe attacker needs local access or must trick a user into running something.
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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.3HighCNA (emc.com)
CVSS 3.17.8HighNVD

Official description

Dell Rugged Control Center, version prior to 4.7, contains an Improper Access Control vulnerability. A local malicious standard user could potentially exploit this vulnerability to modify the content in an unsecured folder when product installation repair is performed, leading to privilege escalation on the system.

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

The underlying weakness: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How developers prevent this class of flaw

  • Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

More Improper Access Control vulnerabilities (CWE-284)

Timeline

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

References

Other vulnerabilities in Rugged Control Center (RCC)

All Rugged Control Center (RCC) vulnerabilities

Recent Improper Access Control vulnerabilities

Spotted an error? Tell us.