Lack of Administrator Control over Security

Draft Class
Structure: Simple
Description

This weakness occurs when a system's built-in security settings cannot be adjusted by its administrator. This prevents tailoring security to the specific deployment environment, forcing the system to operate at a lower or inappropriate security level than required.

Extended Description

When administrators lack continuous control over security configurations, they cannot effectively defend the system against evolving threats. This includes threats from external attackers or even the original software vendor. For example, hard-coded credentials that cannot be changed create a permanent backdoor that the admin is powerless to close, making targeted security hardening impossible. This rigidity forces the organization to accept the developer's default risk posture, which often doesn't match real-world needs. It prevents implementing least-privilege principles, adapting to new compliance rules, or responding to incident investigations. Ultimately, the product becomes a liability instead of a protected asset, as security decisions are outsourced and frozen in time.

Common Consequences 1
Scope: Other

Impact: Varies by Context

Demonstrative Examples 1

ID : DX-14

The following code is an example of an internal hard-coded password in the back-end:

Code Example:

Bad
C
c

Code Example:

Bad
Java
java
Every instance of this program can be placed into diagnostic mode with the same password. Even worse is the fact that if this program is distributed as a binary-only distribution, it is very difficult to change that password or disable this "functionality."
Observed Examples 2
CVE-2022-29953Condition Monitor firmware has a maintenance interface with hard-coded credentials
CVE-2000-0127GUI configuration tool does not enable a security option when a checkbox is selected, although that option is honored when manually set in the configuration file.
Modes of Introduction
Architecture and Design
Implementation