This topic describes the preconfigured "built-in" Test Configurations that are included with C++test.
C++test includes a set of preconfigured "built-in" Test Configurations representing most common test scenarios. You can further customize these configurations as needed by copying and modifying the built-in configurations, or by creating new user-defined configurations from scratch. User-defined Test Configurations can be placed in the User-defined or Team category. User-defined Test Configurations are stored on the local machine and are available for all tests performed by the local C++test installation. Team Test Configurations are stored on the team’s Team Server and can be accessed by all team members.
Static Analysis Group
This group includes universal static analysis test configurations. See Compliance Packs for test configurations that enforce coding standards
| Test Configuration | Description |
|---|---|
| Recommended Rules | The default configuration of recommended rules. Covers most Severity 1 and Severity 2 rules. Includes rules in the Flow Analysis Fast configuration. |
| Flow Analysis Standard | Detects complex runtime errors without requiring test cases or application execution. Defects detected include using uninitialized or invalid memory, null pointer dereferencing, array and buffer overflows, division by zero, memory and resource leaks, and dead code. This requires a special Flow Analysis license option. See Introducing Built-in Flow Analysis Test Configurations for more details on Flow Analysis Test Configurations. |
| Flow Analysis Fast | The fast configuration uses "Shallowest" depth of analysis and runs faster than the standard and aggressive configurations. The fast configuration finds a moderate amount of problems and prevents violation number explosion. See Introducing Built-in Flow Analysis Test Configurations for more details on Flow Analysis Test Configurations. |
| Flow Analysis Aggressive | The aggressive option reports any suspicious code as a violation. See Introducing Built-in Flow Analysis Test Configurations for more details on Flow Analysis Test Configurations. |
| Effective C++ | Checks rules from Scott Meyers’ "Effective C++" book. These rules check the efficiency of C++ programs. |
| Effective STL | Checks rules from Scott Meyers’ "Effective STL" book. |
| Modern C++ (11, 14 and 17) | Checks rules that enforce best practices for modern C++ standards (C++11, C++14, C++17). |
| Find Duplicated Code | Detects duplicated functions, code fragments, string literals, and #include directives. |
| Find Unused Code | Includes rules for identifying unused/dead code. |
| Metrics | Reports metrics statistics and detects metric values out of acceptable ranges. |
| Global Analysis | Checks the Global Static Analysis rules. |
| Sutter-Alexandrescu | Checks rules based on the book "C++ Coding Standards," by Herb Sutter and Andrei Alexandrescu. |
| The Power of Ten | Checks rules based on Gerard J. Holzmann’s article "The Power of Ten - Rules for Developing Safety Critical Code." (http://spinroot.com/gerard/pdf/Power_of_Ten.pdf) |
Compliance Packs
Compliance Packs include test configurations tailored for particular compliance domains to help you enforce industry-specific compliance standards and practices. See Compliance Packs Rule Mapping for information how the standards are mapped to C/C++test's rules.
Aerospace Pack
| Test Configuration | Description |
|---|---|
| Joint Strike Fighter | Checks rules that enforce the Joint Strike Fighter (JSF) program coding standards. |
| DO178C Software Level A Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for DO178C Software Level A |
| DO178C Software Level B Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for DO178C Software Level B |
| DO178C Software Level C and D Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for DO178C Software Level C and D |
Automotive Pack
| Test Configuration | Description |
|---|---|
| AUTOSAR C++14 Coding Guidelines | Checks rules that enforce the AUTOSAR C++ Coding Guidelines (Adaptive Platform, version 19.03).
|
| High Integrity C++ | Checks rules that enforce the High Integrity C++ Coding Standard. |
| HIS Source Code Metrics | Checks metrics required by the Herstellerinitiative Software (HIS) group. |
| MISRA C 1998 | Checks rules that enforce the MISRA C coding standards. |
| MISRA C 2004 | Checks rules that enforce the MISRA C 2004 coding standards. |
| MISRA C++ 2008 | Checks rules that enforce the MISRA C++ 2008 coding standards. |
| MISRA C 2012 | Checks rules that enforce the MISRA C 2012 coding standards.
|
| ISO26262 ASIL A Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for ISO26262 ASIL A |
| ISO26262 ASIL B and C Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for ISO26262 ASIL B and C |
| ISO26262 ASIL D Unit Testing | Executes unit tests with appropriate configuration of coverage metrics and reporting settings for ISO26262 ASIL D |
This test configuration is part of Parasoft Compliance Pack solution that allows you to monitor compliance with industry standards using the "Compliance" extensions on DTP. It requires dedicated license features to be activated. Contact your Parasoft representative for details.Medical Devices Pack
| Test Configuration | Description |
|---|---|
| Recommended Rules for FDA (C) | Checks rules recommended for complying with the FDA General Principles for Software Validation (test configuration for the C language). |
| Recommended Rules for FDA (C++) | Checks rules recommended for complying with the FDA General Principles for Software Validation (test configuration for the C++ language). |
Security Pack
| Test Configuration | Description |
|---|---|
| CWE Top 25 2019 | Includes rules that find issues classified as Top 25 Most Dangerous Programming Errors of the CWE standard.
|
| CWE Top 25 2019 + On the Cusp | Includes rules that find issues classified as Top 25 Most Dangerous Programming Errors of the CWE standard or included on the CWE Weaknesses On the Cusp list.
|
| OWASP Top 10 2017 | Includes rules that find issues identified in OWASP’s Top 10 standard.
|
| Payment Card Industry Data Security Standard | Checks rules for the security issues referenced in section 6 of the Payment Card Industry Data Security Standard (PCI DSS) (https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml) Issues detected include input validation (to prevent cross-site scripting, injection flaws, malicious file execution, etc.) and validation of proper error handling. |
| Security Rules | Checks rules designed to prevent or identify security vulnerabilities. |
| SEI CERT C Coding Guidelines | Checks rules and recommendations for the SEI CERT C Coding Standard. This standard provides guidelines for secure coding. The goal is to facilitate the development of safe, reliable, and secure systems by, for example, eliminating undefined behaviors that can lead to undefined program behaviors and exploitable vulnerabilities. |
| SEI CERT C Rules | Checks rules for the SEI CERT C Coding Standard. This standard provides guidelines for secure coding. The goal is to facilitate the development of safe, reliable, and secure systems by, for example, eliminating undefined behaviors that can lead to undefined program behaviors and exploitable vulnerabilities.
|
| SEI CERT C++ Rules | Checks rules for the SEI CERT C++ Coding Standard. This standard provides guidelines for secure coding. The goal is to facilitate the development of safe, reliable, and secure systems by, for example, eliminating undefined behaviors that can lead to undefined program behaviors and exploitable vulnerabilities.
|
| UL 2900 | Includes rules that find issues identified in the UL-2900 standard. |
Unit Testing Group
| Test Configuration | Description |
|---|---|
| File Scope> Build Test Executable (File Scope) | Builds test executable for "trial builds." Only the selected file(s) will be instrumented. |
| File Scope> Collect Stub Information (File Scope) | Collects symbols data to populate the Stubs view. Only the selected file(s) will be instrumented. |
| File Scope> Debug Unit Tests (File Scope) | Executes unit tests under the debugger. Only the selected file(s) will be instrumented. |
| File Scope> Generate Stubs (File Scope) | Generates stubs for missing function and variable definitions. Only the selected file(s) will be instrumented. |
| File Scope> Run Unit Tests | Executes the available test cases. Only the selected file(s) will be instrumented. |
| Build Test Executable | Builds test executable for "trial builds." All project files will be instrumented. |
| Collect Stub Information | Collects symbols data to populate the Stubs view. All project files will be instrumented. |
| Debug Unit Tests | Executes unit tests under the debugger. All project files will be instrumented. |
| Generate Regression Base | Generates a baseline test suite that captures the project code’s current functionality; to detect changes from this baseline, you run your evolving code base against this test suite on a regular basis. Outcomes are automatically verified. |
| Generate Stubs | Generates stubs for missing function and variable definitions. All project files will be instrumented. |
| Generate Test Suites | Generates test suites (without generating test cases) for the selected resources. |
| Generate Unit Tests | Generates unit tests for the selected resources. |
| Run Unit Tests | Executes the available test cases. All project files will be instrumented. |
| Run Unit Tests with Memory Monitoring | Executes the available test cases and collects information about memory problems. All project files will be instrumented. |
Run Unit Tests in Container | Executes test cases using the toolchain and testing environment in a Docker container (see Analysis and Testing with a Docker Container). |
Application Monitoring Group
| Test Configuration | Description |
|---|---|
| Build Application with Coverage Monitoring | Builds the tested application with coverage monitoring enabled. |
| Build Application with Full Monitoring | Builds the tested application with coverage and memory monitoring enabled. |
| Build Application with Memory Monitoring | Builds the tested application with memory monitoring enabled. |
| Build and Run Application with Coverage Monitoring | Builds and executes the tested application with coverage monitoring enabled. |
| Build and Run Application with Full Monitoring | Builds and executes the tested application with coverage and memory monitoring enabled. |
| Build and Run Application with Memory Monitoring | Builds and executes the tested application with memory monitoring enabled. |
Embedded Systems Group
| Test Configuration | Description |
|---|---|
| ARM > Run ARM Embedded Linux Application with Memory Monitoring | Builds and executes tested applications on ARM Embedded Linux systems (on real target devices or simulators) with coverage and memory monitoring enabled. Test execution results are saved on the target machine file system and are copied to the host using the scp command. |
| ARM > Run ARM Embedded Linux Test Executable | Builds and executes unit tests using the SSH protocol (on real target devices or simulators). Test execution results are saved on the target machine file system and are copied to the host using the scp command. |
| ARM > Run DS-5 2.2 Application with Memory Monitoring | Builds and executes the tested application on the DS-5 Debugger with coverage and memory monitoring enabled. |
| ARM > Run DS-5 2.2 Tests | Builds and executes unit tests using the DS-5 Debugger and collects results. |
| ARM > Run DS-5 3.x 4.x Application with Memory Monitoring | Builds and executes the tested application on the DS-5 Debugger with coverage and memory monitoring enabled. It generates a temporary debugger script with information about how the test binary should be started and starts the debugger with the generated script. You may need to customize the debugger connection name that is passed to the debugger script via the "Target connection configuration" test flow property. |
| ARM > Run DS-5 3.x 4.x Tests | Builds and executes unit tests using the DS-5 Debugger and collects results. It generates a temporary debugger script with information about how the test binary should be started and starts the debugger with the generated script. You may need to customize the debugger connection name that is passed to the debugger script via the "Target connection configuration" test flow property, |
| Arm > Run DS-5 Application with Memory Monitoring (Software Model) | Builds and executes the tested application on the Software Model simulator. With coverage and memory monitoring enabled. You may select the name (executable) of the Model. |
| Arm > Run DS-5 Test Executable (Software Model) | Builds and executes unit test using the Software Model simulator. You may select the name (executable) of the Model. |
| Altium> Run Altium TASKING CTC Application with Mem Monitoring | Builds and executes the tested application using the TASKING standalone debugger (dbgtc) on the TriCore instruction set simulator. Coverage and memory monitoring is enabled. Results from test execution on the simulator are saved on the host machine file system. |
| Altium> Run Altium TASKING CTC Application with Mem Monitoring - CrossView | Builds and executes the tested application using the TASKING Cross View Pro debugger (by default on the TriCore instruction set simulator). Coverage and memory monitoring is enabled. Results from test execution on the simulator are saved on the host machine file system. |
| Altium> Run Altium TASKING CTC Tests | Builds and executes the unit tests using the TASKING standalone debugger (dbgtc) on the TriCore instruction set simulator. Results from test execution on the simulator are saved on the host machine file system. |
| Altium> Run Altium TASKING CTC Tests - CrossView | Builds and executes the unit tests using the TASKING Cross View Pro debugger (by default on the TriCore instruction set simulator). Results from test execution on the simulator are saved on the host machine file system. |
| Spansion> Build and Run Application with Memory Monitoring for Spansion FR Softune - Simulator | Builds and runs the Softune application on the simulator with memory monitoring enabled. Results from test execution are saved on the host machine file system. |
| Spansion> Run Spansion FR Softune Tests - Simulator | Builds and executes unit tests using the Softune debugger on the simulator. Results from test execution are saved on the host machine file system. |
| GNU GCC>Run GNU GCC Tests with Assembly Coverage Monitoring | An all-in-one configuration for GNU GCC compilers targeted for Linux x86 (32bit) that executes unit tests with assembly coverage monitoring. |
| Green Hills Software> Run GHS Tests | An all-in-one configuration for GHS MULTI Embedded that builds the test binary, launches it, and reads the runtime logs. |
| Green Hills Software> Run GHS Application with Mem Monitoring | An all-in-one configuration for GHS MULTI Embedded that builds the test binary in application mode with memory monitoring enabled, launches it, and reads the runtime logs. |
| Green Hills Software> Run GHS Tests with Assembly Coverage Monitoring | An all-in-one configuration for GHS MULTI Embedded that builds the test binary, launches it, and reads the runtime logs. Assembly coverage is collected in addition to unit tests results |
| IAR Systems> Run IAR ARM Application with Mem Monitoring | An all-in-one configuration that builds the test binary in application mode with memory monitoring enabled, launches it, and reads the runtime logs. Uses manual simulator configuration. |
| IAR Systems> Run IAR ARM Tests | An all-in-one configuration that builds the test binary, launches it, and reads the runtime logs. Uses manual simulator configuration. |
| IAR Systems> Run IAR EW Application with Mem Monitoring (Batch Template) | An all-in-one configuration that builds the test binary in application mode with memory monitoring enabled, launches it, and reads the runtime logs. Uses EW-generated batch scripts. |
| IAR Systems> Run IAR EW Tests (Batch Template) | An all-in-one configuration that builds the test binary, launches it, and reads the runtime logs. Uses EW-generated batch scripts. |
| IAR Systems> Run IAR MSP430 Application with Mem Monitoring | An all-in-one configuration that builds the test binary in application mode with memory monitoring enabled, launches it, and reads the runtime logs. Uses manual simulator configuration. |
| IAR Systems> Run IAR MSP430 Tests | An all-in-one configuration that builds the test binary, launches it, and reads the runtime logs. Uses manual simulator configuration. |
| IAR Systems > Run IAR RX Application with Mem Monitoring | An all-in-one configuration that builds the test binary in application mode with memory monitoring enabled, launches it and reads the runtime logs. Uses manual simulator configuration. |
| IAR Systems > Run IAR RX Tests | An all-in-one configuration that builds the test binary, launches it and reads the runtime logs. Uses manual simulator configuration. |
| Keil uVision > Run Keil uVision Tests - ULINK2 (UART) | Builds and executes unit tests using the uVision Debugger and collects results via the RS232 connection. Serial port listener is used to capture the results transmission. You may need to customize the serial connection parameters |
| Keil uVision > Run Keil uVision Tests - ULINKPro or Simulator (ITM) | Builds and executes unit tests using the uVision Debugger and collects results via the ITM based communication channel. |
| Keil uVision > Run Keil uVision Tests - Simulator (UART) | Builds and executes unit tests using the uVision Debugger and simulator. Results are collected and sent via the simulated UART. You may need to customize the serial connection parameters |
| Keil uVision > Run Keil uVision Application with Memory Monitoring - ULINK2 (UART) | Builds and executes the tested application using the uVision Debugger with coverage and memory monitoring enabled. Results are collected via the RS232 connection. Serial port listener is used to capture the results transmission. You may need to customize the serial connection parameters |
| Keil uVision > Run Keil uVision Application with Memory Monitoring - ULINKPro or Simulator (ITM) | Builds and executes the tested application using the uVision Debugger with coverage and memory monitoring enabled. Results are collected via the ITM-based communication channel. |
| Lauterbach Trace32 > Run Application with Memory Monitoring using Trace32 (FDX) | Builds and executes the tested application using the Lauterbach Trace32 debugger. Coverage and memory monitoring is enabled. Results from test execution are saved on the host machine file system (sent via the FDX protocol). By default, the debugger is set to work with the TriCore TC1796 processor. |
| Lauterbach Trace32 > Run Tests using Trace32 (FDX) | Builds and executes the unit tests using the Lauterbach Trace32 debugger. Results from test execution are saved on the host machine file system (sent via the FDX protocol). By default, the debugger is set to work with the TriCore TC1796 processor. |
| QNX > Build and Run Application with Memory Monitoring for QNX Momentics | Builds and executes the tested application on a remote QNX system. You need to customize the remote system properties (remote host, user name and test directory). Communication with the remote system is based on rsh and rcp tools. |
| QNX > Run QNX Momentics Tests | Builds and executes unit tests on a remote QNX system. You need to customize the remote system properties (remote host, user name and test directory). Communication with the remote system is based on rsh and rcp tools. |
| Renesas HEW> Run HEW 4.x Tests (simulated IO) | Builds and executes the unit tests using the HEW debugger on the SH simulator. Results from test execution on the simulator are saved on the host machine file system. |
| Renesas HEW> Run HEW 4.x Application with Mem Monitoring (simulated IO) | Builds and executes the tested application using the HEW debugger on the SH simulator. Coverage and memory monitoring is enabled. Results from test execution on the simulator are saved on the host machine file system. |
| Texas Instruments > Run TI CCS 4.x Application with Memory Monitoring | Builds and executes the tested application in the Code Composer Debugger with coverage and memory monitoring enabled. It will automatically detect the CCS project's active target configuration. |
| Texas Instruments > Run TI CCS 4.x Tests | Builds and executes unit tests using the Code Composer Debugger and collects results. It will automatically detect the CCS project's active target configuration. |
| Wind River> Tornado> Build VxWorks Test Object (PassFS) | Builds a test object that uses the Pass-through File System for storing results. This includes generating and reading static coverage data (if enabled), but not launching the test object or reading any dynamic data. |
| Wind River> Tornado> Build VxWorks Test Object (Socket) | Builds a test object that uses Sockets for transferring and storing results. This includes generating and reading static coverage data (if enabled), but not launching the test object or reading any dynamic data. |
| Wind River> Tornado> Build VxWorks Test Object (TSFS) | Builds a test object that uses the Target Server File System. This includes generating and reading static coverage data (if enabled), but not launching the test object or reading any dynamic data. |
| Wind River> Tornado> Load and Run VxWorks Test Object | Launches your test object using the Wind River Shell. Use with PassFS and TSFS build configurations. |
| Wind River> Tornado> Load and Run VxWorks Test Object (Socket) | Launches the socket listener and then your test binary using the Wind River Shell. Use with the Socket build configuration. |
Wind River> Tornado> Run VxWorks Application with Mem Monitoring (PassFS) | An all-in-one configuration that builds the test binary in application mode with memory monitoring enabled, launches it, and reads the runtime logs. |
| Wind River> Tornado> Run VxWorks Unit Tests (PassFS) | An all-in-one configuration that builds the test object, launches it and reads the runtime logs. |
Wind River> Workbench 3.x> Build VxWorks Test Executable - RTP (PassFS) | Used to prepare a test binary in the form of a Real Time Process executable file. PassFS will be used to store test results. |
| Wind River> Workbench 3.x> Build VxWorks Test Executable - RTP (Socket) | Used to prepare a test binary in the form of a Real Time Process executable file. TCP/IP sockets will be used to send test results. |
| Wind River> Workbench 3.x> Build VxWorks Test Executable - RTP (TSFS) | Used to prepare a test binary in form of Real Time Process executable file. TSFS will be used to store test results. |
| Wind River> Workbench 3.x> Build VxWorks Test Module - DKM (PassFS) | Builds the test binary in the form of a downloadable kernel module, including ctdt.c file generation. When testing with C++test, you may need to exclude the original cdtd.c file from the build to avoid conflicts between the original build ctdt.c and the C++test-generated one. PassFS will be used to store test results. |
| Wind River> Workbench 3.x> Load and Run VxWorks Test Executable (RTP) | Runs the test binary on VxSim. |
| Wind River> Workbench 3.x> Load and Run VxWorks Test Object (DKM) | Runs the test binary on VxSim. |
| Wind River> Workbench 3.x> Run VxWorks Application with Mem Monitoring - DKM (PassFS) | An all-in-one configuration that builds the test binary in the form of a Downloadable Kernel Module in application mode with memory monitoring enabled, launches it and reads the runtime logs. PassFS is used to store test results. |
| Wind River> Workbench 3.x> Run VxWorks Application with Mem Monitoring - DKM (TSFS) | An all-in-one configuration that builds the test binary in the form of a Downloadable Kernel Module in application mode with memory monitoring enabled, launches it, and reads the runtime logs. TSFS is used to store test results. |
| Wind River> Workbench 3.x> Run VxWorks Application with Mem Monitoring - RTP (PassFS) | An all-in-one configuration that builds the test binary in the form of a Real Time Process in application mode with memory monitoring enabled, launches it, and reads the runtime logs. PassFS is used to store test results. |
| Wind River> Workbench 3.x> Run VxWorks Application with Mem Monitoring - RTP (TSFS) | An all-in-one configuration that builds the test binary in the form of a Real Time Process in application mode with memory monitoring enabled, launches it, and reads the runtime logs. TSFS is used to store test results. |
| Wind River> Workbench 4.x> Run VxWorks DKM Application with Full Monitoring (File System, WRWB 4.x) | An all-in-one configuration for WRWB 4.x that builds the test binary in the form of a Downloadable Kernel Module in application mode, loads the binary into the target, runs the test binary, unloads the binary from the target, and collects coverage and runtime monitoring results. |
| Wind River> Workbench 4.x>Run VxWorks DKM Unit Tests (File System, WRWB 4.x) | An all-in-one configuration for WRWB 4.x that builds the test binary in the form of a Downloadable Kernel Module, loads the binary into the target, executes unit tests, unloads the binary from the target, and collects coverage and test results. |
| Wind River> Workbench 4.x> Run VxWorks RTP Application with Full Monitoring (File System, WRWB 4.x) | An all-in-one configuration for WRWB 4.x that builds the test binary in the form of a Real Time Process in application mode, loads the binary into the target, runs the test binary, unloads the binary from the target, and collects coverage and runtime monitoring results. |
| Wind River> Workbench 4.x> Run VxWorks RTP Unit Tests (File System, WRWB 4.x) | An all-in-one configuration for WRWB 4.x that builds the test binary in the form of a Real Time Process, loads the binary into the target, executes unit tests, unloads the binary from the target, and collects coverage and test results. |
| Wind River> Extract Symbols from VxWorks Image | Extracts symbols from a selected VxWorks image. The extracted symbols should be used when testing DKM projects with test configurations from the Wind River> Workbench 3.x group. |
| Build Test Executable - Generic Embedded System |
Utilities Group
| Test Configuration | Description |
|---|---|
| Load Test Results (File) | Used to collect test results via the file channel. By default, this configuration assumes that logs are located inside |
| Load Test Results (Sockets) | Used for "on the fly" collection of test results sent through TCP/IP sockets. It starts a java utility program to listen to and capture test results. You can customize the port numbers for test and coverage results. Port numbers are defined with the results_port and coverage_port properties. |
| Extract Library Symbols | Used to extract a list of symbols from external libraries (or object files). It should be used whenever C++test’s standard algorithm for collecting information about symbols from binaries is not sufficient. For example if you use a Wind River DKM type of project, you may want to have all symbols from the VxWorks image collected in this way. You will probably need to enter the location of the binaries you want to extract symbols from, as well as the name of the nm-like utility that can be used to dump the content of library/object file. |
| Generate Stubs Using External Library Symbols | Used to generate stubs after the "Extract Library Symbols" Test Configuration has been run. It assumes that a file with a list of symbols from external libraries is stored in the project temporary data. |
| Load Application Coverage | Used to import the coverage data collected with the cpptestcc coverage tool into your IDE; see Collecting Application Coverage with cpptestcc. |
| Load Archived Results | Used to load the archived results into C/C++test; see Merging Results from Multiple Test Runs. |
See Configuring Test Configurations and Rules for Policies to learn how to develop custom Test Configurations that are tailored to your projects and team priorities.
Compliance Packs Rule Mapping
This section includes rule mapping for the CWE standard. The mapping information for other standards is available in the PDF rule mapping files shipped with Compliance Packs.
CWE Top 25 Mapping
CWE ID | CWE Name | Parasoft rule ID(s) |
|---|---|---|
CWE-119 | Improper Restriction of Operations within the Bounds of a Memory Buffer |
|
CWE-79 | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | N/A |
CWE-20 | Improper Input Validation |
|
CWE-200 | Information Exposure |
|
CWE-125 | Out-of-bounds Read |
|
CWE-89 | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') |
|
CWE-416 | Use After Free |
|
CWE-190 | Integer Overflow or Wraparound |
|
CWE-352 | Cross-Site Request Forgery (CSRF) | N/A |
CWE-22 | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') |
|
CWE-78 | Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') |
|
CWE-787 | Out-of-bounds Write |
|
CWE-287 | Improper Authentication |
|
CWE-476 | NULL Pointer Dereference |
|
CWE-732 | Incorrect Permission Assignment for Critical Resource |
|
CWE-434 | Unrestricted Upload of File with Dangerous Type | N/A |
CWE-611 | Improper Restriction of XML External Entity Reference |
|
CWE-94 | Improper Control of Generation of Code ('Code Injection') | N/A |
CWE-798 | Use of Hard-coded Credentials |
|
CWE-400 | Uncontrolled Resource Consumption |
|
CWE-772 | Missing Release of Resource after Effective Lifetime |
|
CWE-426 | Untrusted Search Path |
|
CWE-502 | Deserialization of Untrusted Data | N/A |
CWE-269 | Improper Privilege Management |
|
CWE-295 | Improper Certificate Validation | N/A |
CWE Weaknesses On the Cusp Mapping
CWE ID | CWE Name | Parasoft rule ID(s) |
|---|---|---|
CWE-835 | Loop with Unreachable Exit Condition ('Infinite Loop') |
|
CWE-522 | Insufficiently Protected Credentials | N/A |
CWE-704 | Incorrect Type Conversion or Cast |
|
CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') |
|
CWE-918 | Server-Side Request Forgery (SSRF) | N/A |
CWE-415 | Double Free |
|
CWE-601 | URL Redirection to Untrusted Site ('Open Redirect') | N/A |
CWE-863 | Incorrect Authorization |
|
CWE-862 | Missing Authorization | N/A |
CWE-532 | Inclusion of Sensitive Information in Log Files |
|
CWE-306 | Missing Authentication for Critical Function | N/A |
CWE-384 | Session Fixation | N/A |
CWE-326 | Inadequate Encryption Strength |
|
CWE-770 | Allocation of Resources Without Limits or Throttling |
|
CWE-617 | Reachable Assertion |
|
