[Forgot Password]
Login  Register Subscribe

30192

 
 

423868

 
 

233697

 
 

909

 
 

186637

 
 

207

 
 
 
Paid content will be excluded from the download.

Filter
Matches : 909 Download | Alert*

Weaknesses in this category are organized based on which phase they are introduced during the software development and deployment process.

ASP.NET framework/language related environment issues with security implications.

Weaknesses in this category are caused by inadequately implemented input validation within particular technologies.

This view provides an organizational structure for weaknesses that is different than the approaches undertaken by taxonomies such as Seven Pernicious Kingdoms.&&This view is intended to facilitate research into weaknesses, including their inter-dependencies and their role in vulnerabilities. It classifies weaknesses in a way that largely ignores how they can be detected, wh ...

Weaknesses in this category are caused by inadequately implemented protection mechanisms that use the STRUTS framework.

The application uses multiple validation forms with the same name, which might cause the Struts Validator to validate a form that the programmer does not expect.

The application has a validator form that either does not define a validate() method, or defines a validate() method but does not call super.validate().

If a form bean does not extend an ActionForm subclass of the Validator framework, it can expose the application to other weaknesses related to insufficient input validation.

The application has a form field that is not validated by a corresponding validation form, which can introduce other weaknesses related to insufficient input validation.

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.


Pages:      Start    1    2    3    4    5    6    7    8    9    10    11    12    13    14    ..   90

© SecPod Technologies