CWE-103 Variante Rascunho

Struts: Incomplete validate() Method Definition

This vulnerability occurs in a Struts application when a validator form either completely omits a validate() method or includes one but fails to call super.validate() within it.

Definição

What is CWE-103?

This vulnerability occurs in a Struts application when a validator form either completely omits a validate() method or includes one but fails to call super.validate() within it.
In the Struts validation framework, the super.validate() call is essential because it triggers the framework's built-in validation logic. Without this call, the framework cannot process the validation rules defined for the form, effectively leaving the form's input unchecked and allowing potentially malicious or malformed data to proceed. As a result, the entire validation layer for that specific form is disabled, creating a security gap where attackers can bypass intended data checks. Developers must ensure every custom validate() method explicitly invokes super.validate() to maintain the security chain and enforce all configured validation constraints.
Impacto no mundo real

Real-world CVEs caused by CWE-103

Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.

Como os atacantes a exploram

Trajeto do atacante passo a passo

  1. 1

    Identificar um caminho de código que trata input não confiável sem validação.

  2. 2

    Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.

  3. 3

    Entregar o payload através de um pedido normal e observar a reação da aplicação.

  4. 4

    Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.

Exemplo de código vulnerável

Vulnerable Java

In the following Java example the class RegistrationForm is a Struts framework ActionForm Bean that will maintain user input data from a registration webpage for an online business site. The user will enter registration data and the RegistrationForm bean in the Struts framework will maintain the user data. Tthe RegistrationForm class implements the validate method to validate the user input entered into the form.

Vulnerável Java 
public class RegistrationForm extends org.apache.struts.validator.ValidatorForm {
  	// private variables for registration form
  	private String name;
  	private String email;
  	...
  	public RegistrationForm() {
  		super();
  	}
  	public ActionErrors validate(ActionMapping mapping, HttpServletRequest request) {
  		ActionErrors errors = new ActionErrors();
  		if (getName() == null || getName().length() < 1) {
  			errors.add("name", new ActionMessage("error.name.required"));
  		}
  		return errors;
  	}
  	// getter and setter methods for private variables
  	...
  }
Exemplo de código seguro

Secure Java

Although the validate method is implemented in this example the method does not call the validate method of the ValidatorForm parent class with a call super.validate(). Without the call to the parent validator class only the custom validation will be performed and the default validation will not be performed. The following example shows that the validate method of the ValidatorForm class is called within the implementation of the validate method.

Seguro Java 
public class RegistrationForm extends org.apache.struts.validator.ValidatorForm {
  		// private variables for registration form
  		private String name;
  		private String email;
  		...
  		public RegistrationForm() {
  			super();
  		}
  		public ActionErrors validate(ActionMapping mapping, HttpServletRequest request) {
  			ActionErrors errors = super.validate(mapping, request);
  			if (errors == null) {
  				errors = new ActionErrors();
  			}
  		if (getName() == null || getName().length() < 1) {
  			errors.add("name", new ActionMessage("error.name.required"));
  		}
  		return errors;
  }
  	// getter and setter methods for private variables
  	...
  }
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-103

  • Implementation Implement the validate() method and call super.validate() within that method.
Sinais de deteção

How to detect CWE-103

Automated Static Analysis High

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Correção automática do Plexicus

O Plexicus deteta automaticamente o CWE-103 e abre um PR de correção em menos de 60 segundos.

O Codex Remedium analisa cada commit, identifica esta fraqueza exata e entrega um pull request pronto para revisão com o patch. Sem tickets. Sem transferências.

Obter uma demonstração Experimente o Plexicus gratuitamente
Perguntas frequentes

Frequently asked questions

O que é o CWE-103?

This vulnerability occurs in a Struts application when a validator form either completely omits a validate() method or includes one but fails to call super.validate() within it.

Qual a gravidade do CWE-103?

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-103?

MITRE lists the following affected platforms: Java.

Como posso prevenir o CWE-103?

Implement the validate() method and call super.validate() within that method.

Como é que o Plexicus deteta e corrige o CWE-103?

O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-103 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-103?

A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/103.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.

Fraquezas relacionadas

Weaknesses related to CWE-103

CWE-573 Pai

Improper Following of Specification by Caller

This weakness occurs when software fails to properly follow the documented rules, protocols, or requirements of an external component it…

CWE-104 Irmão

Struts: Form Bean Does Not Extend Validation Class

This vulnerability occurs in Apache Struts applications when a form bean class does not properly extend the framework's validation class.…

CWE-243 Irmão

Creation of chroot Jail Without Changing Working Directory

This vulnerability occurs when a program creates a chroot jail but fails to change its current working directory afterward. Because the…

CWE-253 Irmão

Incorrect Check of Function Return Value

This vulnerability occurs when a program misinterprets or improperly validates the return value from a function, causing it to miss…

CWE-296 Irmão

Improper Following of a Certificate's Chain of Trust

This vulnerability occurs when software fails to properly validate the entire certificate chain back to a trusted root authority. This…

CWE-304 Irmão

Missing Critical Step in Authentication

This vulnerability occurs when a software authentication process omits a required step, weakening its overall security.

CWE-325 Irmão

Missing Cryptographic Step

This vulnerability occurs when a software implementation skips a critical step in a cryptographic process, resulting in security that is…

CWE-329 Irmão

Generation of Predictable IV with CBC Mode

This vulnerability occurs when software uses a predictable or reused Initialization Vector (IV) with Cipher Block Chaining (CBC) mode…

CWE-358 Irmão

Improperly Implemented Security Check for Standard

This vulnerability occurs when software fails to correctly implement one or more critical security checks required by a standard protocol,…

Recursos

Further reading

Pronto quando você estiver

Pare de pagar por desenvolvedor.
Comece a fechar o ciclo.

O Plexicus é o ASPM nativo de IA que verifica, filtra, corrige, pentesta e explica — de forma autónoma. Programadores ilimitados, repos ilimitados, ações de IA de utilização justa. Nível gratuito real, €269/mo anual quando estiver pronto.

Começar grátis Reservar uma demo