Struts: Plug-in Framework not in Use

Opis

When an application does not use an input validation framework such as the Struts Validator, there is a greater risk of introducing weaknesses related to insufficient input validation.

Unchecked input is the leading cause of vulnerabilities in J2EE applications. Unchecked input leads to cross-site scripting, process control, and SQL injection vulnerabilities, among others.

Although J2EE applications are not generally susceptible to memory corruption attacks, if a J2EE application interfaces with native code that does not perform array bounds checking, an attacker may be able to use an input validation mistake in the J2EE application to launch a buffer overflow attack.

Skutki

• Integrity

  Unexpected State

Zapobieganie

• Architecture and Design · Input Validation

  Use an input validation framework such as Struts.

• Architecture and Design · Libraries or Frameworks

  Use an input validation framework such as Struts.

• Implementation · Input Validation

  Use the Struts Validator to validate all program input before it is processed by the application. Ensure that there are no holes in the configuration of the Struts Validator. Example uses of the validator include checking to ensure that:

  - Phone number fields contain only valid characters in phone numbers

  - Boolean values are only "T" or "F"

  - Free-form strings are of a reasonable length and composition

• Implementation · Libraries or Frameworks

  Use the Struts Validator to validate all program input before it is processed by the application. Ensure that there are no holes in the configuration of the Struts Validator. Example uses of the validator include checking to ensure that:

  - Phone number fields contain only valid characters in phone numbers

  - Boolean values are only "T" or "F"

  - Free-form strings are of a reasonable length and composition

Słabość nadrzędna

• CWE-1173 Improper Use of Validation Framework
• CWE-20 Improper Input Validation

Kiedy powstaje

• Implementation

Dotyczy

Java

Źródła

1. Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors — Katrina Tsipenyuk, Brian Chess, Gary McGraw, NIST, 2005