Lack of Administrator Control over Security
Draft Class
Structure: Simple
Description
The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect the environment in which the product is being used. This introduces resultant weaknesses or prevents it from operating at a level of security that is desired by the administrator.
If the product's administrator does not have the ability to manage security-related decisions at all times, then protecting the product from outside threats - including the product's developer - can become impossible. For example, a hard-coded account name and password cannot be changed by the administrator, thus exposing that product to attacks that the administrator can not prevent.
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
cCode Example:
Bad
Java
javaEvery 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
Related Weaknesses