Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.
CWE-671 Class Draft
Lack of Administrator Control over Security
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…
Definition
What is CWE-671?
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.
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.
Real-world impact
Real-world CVEs caused by CWE-671
-
Condition Monitor firmware has a maintenance interface with hard-coded credentials
-
GUI 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.
How attackers exploit it
Step-by-step attacker path
- 1
Identify a code path that handles untrusted input without validation.
- 2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
- 3
Deliver the payload through a normal request and observe the application's reaction.
- 4
Iterate until the response leaks data, executes attacker code, or escalates privileges.
Vulnerable code example
Vulnerable C
The following code is an example of an internal hard-coded password in the back-end:
int VerifyAdmin(char *password) {
if (strcmp(password, "Mew!")) {
printf("Incorrect Password!\n");
return(0)
}
printf("Entering Diagnostic Mode...\n");
return(1);
} Secure code example
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist
How to prevent CWE-671
- Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
- Implementation Validate input at trust boundaries; use allowlists, not denylists.
- Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
- Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
- Operation Monitor logs for the runtime signals listed in the next section.
Detection signals
How to detect CWE-671
Run dynamic application security testing against the live endpoint.
Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.
Code review: flag any new code that handles input from this surface without using the validated framework helpers.
CWE-671
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Frequently asked questions What is CWE-671?
How serious is CWE-671?
What languages or platforms are affected by CWE-671?
How can I prevent CWE-671?
How does Plexicus detect and fix CWE-671?
Where can I learn more about CWE-671?
Frequently asked questions
What is CWE-671?
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.
How serious is CWE-671?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-671?
MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.
How can I prevent CWE-671?
Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.
How does Plexicus detect and fix CWE-671?
Plexicus's SAST engine matches the data-flow signature for CWE-671 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-671?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/671.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-671
CWE-657 Parent
Violation of Secure Design Principles
This weakness occurs when a system's architecture or design fails to follow fundamental security principles, creating a flawed foundation…
CWE-1192 Sibling
Improper Identifier for IP Block used in System-On-Chip (SOC)
This weakness occurs when a System-on-Chip (SoC) lacks a secure, unique, and permanent identifier for its internal hardware components (IP…
CWE-1395 Sibling
Dependency on Vulnerable Third-Party Component
This vulnerability occurs when your software relies on an external library, framework, or module that contains known security flaws.
CWE-250 Sibling
Execution with Unnecessary Privileges
This vulnerability occurs when software runs with higher permissions than it actually needs to perform its tasks. This excessive privilege…
CWE-636 Sibling
Not Failing Securely ('Failing Open')
This vulnerability occurs when a system, upon encountering an error or failure, defaults to its least secure configuration instead of a…
CWE-637 Sibling
Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')
This weakness occurs when a security feature is implemented with excessive complexity, creating unnecessary risk. Overly intricate…
CWE-638 Sibling
Not Using Complete Mediation
This vulnerability occurs when software fails to verify access permissions every single time a user or process tries to use a resource.…
CWE-653 Sibling
Improper Isolation or Compartmentalization
This vulnerability occurs when an application fails to enforce strong boundaries between components that operate at different security…
CWE-654 Sibling
Reliance on a Single Factor in a Security Decision
This vulnerability occurs when a system's security check depends almost entirely on just one condition, object, or piece of data to decide…
Ready to validate what matters?
Ready to validate what matters?
Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.