|Paid content will be excluded from the download.
| Matches : 909
|This category intends to capture the motivations and intentions
of developers that lead to weaknesses that are found within
Weaknesses in this category were intentionally introduced by
the developer, typically as a result of prioritizing other aspects of the
program over security, such as maintenance.
Nonmalicious introduction of weaknesses into software can still
render it vulnerable to various attacks.
Other kinds of intentional but nonmalicious security flaws are
possible. Functional requirements that are written without regard to security
requirements can lead to such flaws; one of the flaws exploited by the "Internet
worm"  (case U10) could be placed in this category.
The software contains a weakness that was inadvertently
introduced by the developer.
This category lists weaknesses related to environmental
problems in .NET framework applications.
Weaknesses in this category are related to concurrent use of
Weaknesses in this category are related to improper use of
arguments or parameters within function calls.
Weaknesses in this category are related to incorrectly written
expressions within code.
Weaknesses in this category affect file or directory
Pages:      Start    73    74    75    76    77    78    79    80    81    82    83    84    85    86    ..   90
© 2013 SecPod Technologies