Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.
CWE-671 Classe Rascunho
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…
Definição
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.
Impacto no mundo real
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.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
Identificar um caminho de código que trata input não confiável sem validação.
- 2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
- 3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
- 4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.
Exemplo de código vulnerável
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);
} Exemplo de código seguro
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.
Lista de verificação de prevenção
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.
Sinais de deteção
How to detect CWE-671
Executar testes dinâmicos de segurança de aplicações (DAST) contra o endpoint em execução.
Monitorizar os registos em tempo de execução para traços de exceção invulgares, input malformado ou tentativas de contornar a autorização.
Revisão de código: sinalizar qualquer novo código que trate input desta superfície sem usar os ajudantes validados do framework.
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.
Perguntas frequentes O que é o CWE-671?
Qual a gravidade do CWE-671?
Que linguagens ou plataformas são afetadas pelo CWE-671?
Como posso prevenir o CWE-671?
Como é que o Plexicus deteta e corrige o CWE-671?
Onde posso saber mais sobre o CWE-671?
Frequently asked questions
O que é o 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.
Qual a gravidade do CWE-671?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-671?
A MITRE não especificou as plataformas afetadas por este CWE — pode aplicar-se à maioria das stacks de aplicações.
Como posso prevenir o 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.
Como é que o Plexicus deteta e corrige o CWE-671?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-671 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-671?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/671.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-671
CWE-657 Pai
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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 Irmão
Improper Isolation or Compartmentalization
This vulnerability occurs when an application fails to enforce strong boundaries between components that operate at different security…
CWE-654 Irmão
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…
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.