instruction stringlengths 20 156 | context stringclasses 37 values | response stringlengths 73 869 | category stringclasses 11 values | language stringclasses 2 values | difficulty stringclasses 4 values | source stringclasses 8 values | id stringlengths 14 14 |
|---|---|---|---|---|---|---|---|
What is Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1) attack pattern? | CAPEC | Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1): In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be | web_security | en | intermediate | capec | kwcyber_000000 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1)ุ | CAPEC | ูู
ุท ุงููุฌูู
Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1): In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be | web_security | ar | intermediate | capec | kwcyber_000001 |
How does Accessing Functionality Not Properly Constrained by ACLs attack work? | Attack Analysis | Technical analysis of Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1): In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be | web_security | en | advanced | capec | kwcyber_000002 |
What is Buffer Overflow via Environment Variables (CAPEC-10) attack pattern? | CAPEC | Buffer Overflow via Environment Variables (CAPEC-10): This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the adversary finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables. | web_security | en | intermediate | capec | kwcyber_000003 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Buffer Overflow via Environment Variables (CAPEC-10)ุ | CAPEC | ูู
ุท ุงููุฌูู
Buffer Overflow via Environment Variables (CAPEC-10): This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the adversary finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables. | web_security | ar | intermediate | capec | kwcyber_000004 |
How does Buffer Overflow via Environment Variables attack work? | Attack Analysis | Technical analysis of Buffer Overflow via Environment Variables (CAPEC-10): This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the adversary finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables. | web_security | en | advanced | capec | kwcyber_000005 |
What is Overflow Buffers (CAPEC-100) attack pattern? | CAPEC | Overflow Buffers (CAPEC-100): Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice. | web_security | en | intermediate | capec | kwcyber_000006 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Overflow Buffers (CAPEC-100)ุ | CAPEC | ูู
ุท ุงููุฌูู
Overflow Buffers (CAPEC-100): Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice. | web_security | ar | intermediate | capec | kwcyber_000007 |
How does Overflow Buffers attack work? | Attack Analysis | Technical analysis of Overflow Buffers (CAPEC-100): Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice. | web_security | en | advanced | capec | kwcyber_000008 |
What is Server Side Include (SSI) Injection (CAPEC-101) attack pattern? | CAPEC | Server Side Include (SSI) Injection (CAPEC-101): An attacker can use Server Side Include (SSI) Injection to send code to a web application that then gets executed by the web server. Doing so enables the attacker to achieve similar results to Cross Site Scripting, viz., arbitrary code execution and information disclosure, albeit on a more limited scale, since the SSI directives are nowhere near as powerful as a full-fledged scripting language. Nonetheless, the attacker can conveniently gain access to sensitive files, such as password files, and execute shell commands. | web_security | en | intermediate | capec | kwcyber_000009 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Server Side Include (SSI) Injection (CAPEC-101)ุ | CAPEC | ูู
ุท ุงููุฌูู
Server Side Include (SSI) Injection (CAPEC-101): An attacker can use Server Side Include (SSI) Injection to send code to a web application that then gets executed by the web server. Doing so enables the attacker to achieve similar results to Cross Site Scripting, viz., arbitrary code execution and information disclosure, albeit on a more limited scale, since the SSI directives are nowhere near as powerful as a full-fledged scripting language. Nonetheless, the attacker can conveniently gain access to sensitive files, such as password files, and execute shell commands. | web_security | ar | intermediate | capec | kwcyber_000010 |
How does Server Side Include (SSI) Injection attack work? | Attack Analysis | Technical analysis of Server Side Include (SSI) Injection (CAPEC-101): An attacker can use Server Side Include (SSI) Injection to send code to a web application that then gets executed by the web server. Doing so enables the attacker to achieve similar results to Cross Site Scripting, viz., arbitrary code execution and information disclosure, albeit on a more limited scale, since the SSI directives are nowhere near as powerful as a full-fledged scripting language. Nonetheless, the attacker can conveniently gain access to sensitive files, such as password files, and execute shell commands. | web_security | en | advanced | capec | kwcyber_000011 |
What is Session Sidejacking (CAPEC-102) attack pattern? | CAPEC | Session Sidejacking (CAPEC-102): Session sidejacking takes advantage of an unencrypted communication channel between a victim and target system. The attacker sniffs traffic on a network looking for session tokens in unencrypted traffic. Once a session token is captured, the attacker performs malicious actions by using the stolen token with the targeted application to impersonate the victim. This attack is a specific method of session hijacking, which is exploiting a valid session token to gain unauthorized access to a target system or information. Other methods to perform a session hijacking are session fixation, cross-site s | web_security | en | intermediate | capec | kwcyber_000012 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Session Sidejacking (CAPEC-102)ุ | CAPEC | ูู
ุท ุงููุฌูู
Session Sidejacking (CAPEC-102): Session sidejacking takes advantage of an unencrypted communication channel between a victim and target system. The attacker sniffs traffic on a network looking for session tokens in unencrypted traffic. Once a session token is captured, the attacker performs malicious actions by using the stolen token with the targeted application to impersonate the victim. This attack is a specific method of session hijacking, which is exploiting a valid session token to gain unauthorized access to a target system or information. Other methods to perform a session hijacking are session fixation, cross-site s | web_security | ar | intermediate | capec | kwcyber_000013 |
How does Session Sidejacking attack work? | Attack Analysis | Technical analysis of Session Sidejacking (CAPEC-102): Session sidejacking takes advantage of an unencrypted communication channel between a victim and target system. The attacker sniffs traffic on a network looking for session tokens in unencrypted traffic. Once a session token is captured, the attacker performs malicious actions by using the stolen token with the targeted application to impersonate the victim. This attack is a specific method of session hijacking, which is exploiting a valid session token to gain unauthorized access to a target system or information. Other methods to perform a session hijacking are session fixation, cross-site s | web_security | en | advanced | capec | kwcyber_000014 |
What is Clickjacking (CAPEC-103) attack pattern? | CAPEC | Clickjacking (CAPEC-103): An adversary tricks a victim into unknowingly initiating some action in one system while interacting with the UI from a seemingly completely different, usually an adversary controlled or intended, system. | web_security | en | intermediate | capec | kwcyber_000015 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Clickjacking (CAPEC-103)ุ | CAPEC | ูู
ุท ุงููุฌูู
Clickjacking (CAPEC-103): An adversary tricks a victim into unknowingly initiating some action in one system while interacting with the UI from a seemingly completely different, usually an adversary controlled or intended, system. | web_security | ar | intermediate | capec | kwcyber_000016 |
How does Clickjacking attack work? | Attack Analysis | Technical analysis of Clickjacking (CAPEC-103): An adversary tricks a victim into unknowingly initiating some action in one system while interacting with the UI from a seemingly completely different, usually an adversary controlled or intended, system. | web_security | en | advanced | capec | kwcyber_000017 |
What is Cross Zone Scripting (CAPEC-104) attack pattern? | CAPEC | Cross Zone Scripting (CAPEC-104): An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security. | web_security | en | intermediate | capec | kwcyber_000018 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Cross Zone Scripting (CAPEC-104)ุ | CAPEC | ูู
ุท ุงููุฌูู
Cross Zone Scripting (CAPEC-104): An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security. | web_security | ar | intermediate | capec | kwcyber_000019 |
How does Cross Zone Scripting attack work? | Attack Analysis | Technical analysis of Cross Zone Scripting (CAPEC-104): An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security. | web_security | en | advanced | capec | kwcyber_000020 |
What is HTTP Request Splitting (CAPEC-105) attack pattern? | CAPEC | HTTP Request Splitting (CAPEC-105): <xhtml:p>An adversary abuses the flexibility and discrepancies in the parsing and interpretation of HTTP Request messages by different intermediary HTTP agents (e.g., load balancer, reverse proxy, web caching proxies, application firewalls, etc.) to split a single HTTP request into multiple unauthorized and malicious HTTP requests to a back-end HTTP agent (e.g., web server).</xhtml:p> <xhtml:p>See CanPrecede relationships for possible consequences.</xhtml:p> | web_security | en | intermediate | capec | kwcyber_000021 |
ู
ุง ูู ูู
ุท ุงููุฌูู
HTTP Request Splitting (CAPEC-105)ุ | CAPEC | ูู
ุท ุงููุฌูู
HTTP Request Splitting (CAPEC-105): <xhtml:p>An adversary abuses the flexibility and discrepancies in the parsing and interpretation of HTTP Request messages by different intermediary HTTP agents (e.g., load balancer, reverse proxy, web caching proxies, application firewalls, etc.) to split a single HTTP request into multiple unauthorized and malicious HTTP requests to a back-end HTTP agent (e.g., web server).</xhtml:p> <xhtml:p>See CanPrecede relationships for possible consequences.</xhtml:p> | web_security | ar | intermediate | capec | kwcyber_000022 |
How does HTTP Request Splitting attack work? | Attack Analysis | Technical analysis of HTTP Request Splitting (CAPEC-105): <xhtml:p>An adversary abuses the flexibility and discrepancies in the parsing and interpretation of HTTP Request messages by different intermediary HTTP agents (e.g., load balancer, reverse proxy, web caching proxies, application firewalls, etc.) to split a single HTTP request into multiple unauthorized and malicious HTTP requests to a back-end HTTP agent (e.g., web server).</xhtml:p> <xhtml:p>See CanPrecede relationships for possible consequences.</xhtml:p> | web_security | en | advanced | capec | kwcyber_000023 |
What is DEPRECATED: XSS through Log Files (CAPEC-106) attack pattern? | CAPEC | DEPRECATED: XSS through Log Files (CAPEC-106): This attack pattern has been deprecated as it referes to an existing chain relationship between "CAPEC-93 : Log Injection-Tampering-Forging" and "CAPEC-63 : Cross-Site Scripting". Please refer to these CAPECs going forward. | web_security | en | intermediate | capec | kwcyber_000024 |
ู
ุง ูู ูู
ุท ุงููุฌูู
DEPRECATED: XSS through Log Files (CAPEC-106)ุ | CAPEC | ูู
ุท ุงููุฌูู
DEPRECATED: XSS through Log Files (CAPEC-106): This attack pattern has been deprecated as it referes to an existing chain relationship between "CAPEC-93 : Log Injection-Tampering-Forging" and "CAPEC-63 : Cross-Site Scripting". Please refer to these CAPECs going forward. | web_security | ar | intermediate | capec | kwcyber_000025 |
How does DEPRECATED: XSS through Log Files attack work? | Attack Analysis | Technical analysis of DEPRECATED: XSS through Log Files (CAPEC-106): This attack pattern has been deprecated as it referes to an existing chain relationship between "CAPEC-93 : Log Injection-Tampering-Forging" and "CAPEC-63 : Cross-Site Scripting". Please refer to these CAPECs going forward. | web_security | en | advanced | capec | kwcyber_000026 |
What is Cross Site Tracing (CAPEC-107) attack pattern? | CAPEC | Cross Site Tracing (CAPEC-107): Cross Site Tracing (XST) enables an adversary to steal the victim's session cookie and possibly other authentication credentials transmitted in the header of the HTTP request when the victim's browser communicates to a destination system's web server. | web_security | en | intermediate | capec | kwcyber_000027 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Cross Site Tracing (CAPEC-107)ุ | CAPEC | ูู
ุท ุงููุฌูู
Cross Site Tracing (CAPEC-107): Cross Site Tracing (XST) enables an adversary to steal the victim's session cookie and possibly other authentication credentials transmitted in the header of the HTTP request when the victim's browser communicates to a destination system's web server. | web_security | ar | intermediate | capec | kwcyber_000028 |
How does Cross Site Tracing attack work? | Attack Analysis | Technical analysis of Cross Site Tracing (CAPEC-107): Cross Site Tracing (XST) enables an adversary to steal the victim's session cookie and possibly other authentication credentials transmitted in the header of the HTTP request when the victim's browser communicates to a destination system's web server. | web_security | en | advanced | capec | kwcyber_000029 |
What is Command Line Execution through SQL Injection (CAPEC-108) attack pattern? | CAPEC | Command Line Execution through SQL Injection (CAPEC-108): An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new command | web_security | en | intermediate | capec | kwcyber_000030 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Command Line Execution through SQL Injection (CAPEC-108)ุ | CAPEC | ูู
ุท ุงููุฌูู
Command Line Execution through SQL Injection (CAPEC-108): An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new command | web_security | ar | intermediate | capec | kwcyber_000031 |
How does Command Line Execution through SQL Injection attack work? | Attack Analysis | Technical analysis of Command Line Execution through SQL Injection (CAPEC-108): An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new command | web_security | en | advanced | capec | kwcyber_000032 |
What is Object Relational Mapping Injection (CAPEC-109) attack pattern? | CAPEC | Object Relational Mapping Injection (CAPEC-109): An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject their own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are | web_security | en | intermediate | capec | kwcyber_000033 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Object Relational Mapping Injection (CAPEC-109)ุ | CAPEC | ูู
ุท ุงููุฌูู
Object Relational Mapping Injection (CAPEC-109): An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject their own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are | web_security | ar | intermediate | capec | kwcyber_000034 |
How does Object Relational Mapping Injection attack work? | Attack Analysis | Technical analysis of Object Relational Mapping Injection (CAPEC-109): An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject their own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are | web_security | en | advanced | capec | kwcyber_000035 |
What is Cause Web Server Misclassification (CAPEC-11) attack pattern? | CAPEC | Cause Web Server Misclassification (CAPEC-11): An attack of this type exploits a Web server's decision to take action based on filename or file extension. Because different file types are handled by different server processes, misclassification may force the Web server to take unexpected action, or expected actions in an unexpected sequence. This may cause the server to exhaust resources, supply debug or system data to the attacker, or bind an attacker to a remote process. | web_security | en | intermediate | capec | kwcyber_000036 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Cause Web Server Misclassification (CAPEC-11)ุ | CAPEC | ูู
ุท ุงููุฌูู
Cause Web Server Misclassification (CAPEC-11): An attack of this type exploits a Web server's decision to take action based on filename or file extension. Because different file types are handled by different server processes, misclassification may force the Web server to take unexpected action, or expected actions in an unexpected sequence. This may cause the server to exhaust resources, supply debug or system data to the attacker, or bind an attacker to a remote process. | web_security | ar | intermediate | capec | kwcyber_000037 |
How does Cause Web Server Misclassification attack work? | Attack Analysis | Technical analysis of Cause Web Server Misclassification (CAPEC-11): An attack of this type exploits a Web server's decision to take action based on filename or file extension. Because different file types are handled by different server processes, misclassification may force the Web server to take unexpected action, or expected actions in an unexpected sequence. This may cause the server to exhaust resources, supply debug or system data to the attacker, or bind an attacker to a remote process. | web_security | en | advanced | capec | kwcyber_000038 |
What is SQL Injection through SOAP Parameter Tampering (CAPEC-110) attack pattern? | CAPEC | SQL Injection through SOAP Parameter Tampering (CAPEC-110): An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message. | web_security | en | intermediate | capec | kwcyber_000039 |
ู
ุง ูู ูู
ุท ุงููุฌูู
SQL Injection through SOAP Parameter Tampering (CAPEC-110)ุ | CAPEC | ูู
ุท ุงููุฌูู
SQL Injection through SOAP Parameter Tampering (CAPEC-110): An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message. | web_security | ar | intermediate | capec | kwcyber_000040 |
How does SQL Injection through SOAP Parameter Tampering attack work? | Attack Analysis | Technical analysis of SQL Injection through SOAP Parameter Tampering (CAPEC-110): An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message. | web_security | en | advanced | capec | kwcyber_000041 |
What is JSON Hijacking (aka JavaScript Hijacking) (CAPEC-111) attack pattern? | CAPEC | JSON Hijacking (aka JavaScript Hijacking) (CAPEC-111): An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website. | web_security | en | intermediate | capec | kwcyber_000042 |
ู
ุง ูู ูู
ุท ุงููุฌูู
JSON Hijacking (aka JavaScript Hijacking) (CAPEC-111)ุ | CAPEC | ูู
ุท ุงููุฌูู
JSON Hijacking (aka JavaScript Hijacking) (CAPEC-111): An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website. | web_security | ar | intermediate | capec | kwcyber_000043 |
How does JSON Hijacking (aka JavaScript Hijacking) attack work? | Attack Analysis | Technical analysis of JSON Hijacking (aka JavaScript Hijacking) (CAPEC-111): An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website. | web_security | en | advanced | capec | kwcyber_000044 |
What is Brute Force (CAPEC-112) attack pattern? | CAPEC | Brute Force (CAPEC-112): In this attack, some asset (information, functionality, identity, etc.) is protected by a finite secret value. The attacker attempts to gain access to this asset by using trial-and-error to exhaustively explore all the possible secret values in the hope of finding the secret (or a value that is functionally equivalent) that will unlock the asset. | web_security | en | intermediate | capec | kwcyber_000045 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Brute Force (CAPEC-112)ุ | CAPEC | ูู
ุท ุงููุฌูู
Brute Force (CAPEC-112): In this attack, some asset (information, functionality, identity, etc.) is protected by a finite secret value. The attacker attempts to gain access to this asset by using trial-and-error to exhaustively explore all the possible secret values in the hope of finding the secret (or a value that is functionally equivalent) that will unlock the asset. | web_security | ar | intermediate | capec | kwcyber_000046 |
How does Brute Force attack work? | Attack Analysis | Technical analysis of Brute Force (CAPEC-112): In this attack, some asset (information, functionality, identity, etc.) is protected by a finite secret value. The attacker attempts to gain access to this asset by using trial-and-error to exhaustively explore all the possible secret values in the hope of finding the secret (or a value that is functionally equivalent) that will unlock the asset. | web_security | en | advanced | capec | kwcyber_000047 |
What is Interface Manipulation (CAPEC-113) attack pattern? | CAPEC | Interface Manipulation (CAPEC-113): An adversary manipulates the use or processing of an interface (e.g. Application Programming Interface (API) or System-on-Chip (SoC)) resulting in an adverse impact upon the security of the system implementing the interface. This can allow the adversary to bypass access control and/or execute functionality not intended by the interface implementation, possibly compromising the system which integrates the interface. Interface manipulation can take on a number of forms including forcing the unexpected use of an interface or the use of an interface in an unintended way. | web_security | en | intermediate | capec | kwcyber_000048 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Interface Manipulation (CAPEC-113)ุ | CAPEC | ูู
ุท ุงููุฌูู
Interface Manipulation (CAPEC-113): An adversary manipulates the use or processing of an interface (e.g. Application Programming Interface (API) or System-on-Chip (SoC)) resulting in an adverse impact upon the security of the system implementing the interface. This can allow the adversary to bypass access control and/or execute functionality not intended by the interface implementation, possibly compromising the system which integrates the interface. Interface manipulation can take on a number of forms including forcing the unexpected use of an interface or the use of an interface in an unintended way. | web_security | ar | intermediate | capec | kwcyber_000049 |
How does Interface Manipulation attack work? | Attack Analysis | Technical analysis of Interface Manipulation (CAPEC-113): An adversary manipulates the use or processing of an interface (e.g. Application Programming Interface (API) or System-on-Chip (SoC)) resulting in an adverse impact upon the security of the system implementing the interface. This can allow the adversary to bypass access control and/or execute functionality not intended by the interface implementation, possibly compromising the system which integrates the interface. Interface manipulation can take on a number of forms including forcing the unexpected use of an interface or the use of an interface in an unintended way. | web_security | en | advanced | capec | kwcyber_000050 |
What is Authentication Abuse (CAPEC-114) attack pattern? | CAPEC | Authentication Abuse (CAPEC-114): An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. | web_security | en | intermediate | capec | kwcyber_000051 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Authentication Abuse (CAPEC-114)ุ | CAPEC | ูู
ุท ุงููุฌูู
Authentication Abuse (CAPEC-114): An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. | web_security | ar | intermediate | capec | kwcyber_000052 |
How does Authentication Abuse attack work? | Attack Analysis | Technical analysis of Authentication Abuse (CAPEC-114): An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. | web_security | en | advanced | capec | kwcyber_000053 |
What is Authentication Bypass (CAPEC-115) attack pattern? | CAPEC | Authentication Bypass (CAPEC-115): An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authentication mechanism. The attacker is therefore able to access protected data without authentication ever having taken place. | web_security | en | intermediate | capec | kwcyber_000054 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Authentication Bypass (CAPEC-115)ุ | CAPEC | ูู
ุท ุงููุฌูู
Authentication Bypass (CAPEC-115): An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authentication mechanism. The attacker is therefore able to access protected data without authentication ever having taken place. | web_security | ar | intermediate | capec | kwcyber_000055 |
How does Authentication Bypass attack work? | Attack Analysis | Technical analysis of Authentication Bypass (CAPEC-115): An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authentication mechanism. The attacker is therefore able to access protected data without authentication ever having taken place. | web_security | en | advanced | capec | kwcyber_000056 |
What is Excavation (CAPEC-116) attack pattern? | CAPEC | Excavation (CAPEC-116): An adversary actively probes the target in a manner that is designed to solicit information that could be leveraged for malicious purposes. | web_security | en | intermediate | capec | kwcyber_000057 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Excavation (CAPEC-116)ุ | CAPEC | ูู
ุท ุงููุฌูู
Excavation (CAPEC-116): An adversary actively probes the target in a manner that is designed to solicit information that could be leveraged for malicious purposes. | web_security | ar | intermediate | capec | kwcyber_000058 |
How does Excavation attack work? | Attack Analysis | Technical analysis of Excavation (CAPEC-116): An adversary actively probes the target in a manner that is designed to solicit information that could be leveraged for malicious purposes. | web_security | en | advanced | capec | kwcyber_000059 |
What is Interception (CAPEC-117) attack pattern? | CAPEC | Interception (CAPEC-117): An adversary monitors data streams to or from the target for information gathering purposes. This attack may be undertaken to solely gather sensitive information or to support a further attack against the target. This attack pattern can involve sniffing network traffic as well as other types of data streams (e.g. radio). The adversary can attempt to initiate the establishment of a data stream or passively observe the communications as they unfold. In all variants of this attack, the adversary is not the intended recipient of the data stream. In contrast to other means of gathering information | web_security | en | intermediate | capec | kwcyber_000060 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Interception (CAPEC-117)ุ | CAPEC | ูู
ุท ุงููุฌูู
Interception (CAPEC-117): An adversary monitors data streams to or from the target for information gathering purposes. This attack may be undertaken to solely gather sensitive information or to support a further attack against the target. This attack pattern can involve sniffing network traffic as well as other types of data streams (e.g. radio). The adversary can attempt to initiate the establishment of a data stream or passively observe the communications as they unfold. In all variants of this attack, the adversary is not the intended recipient of the data stream. In contrast to other means of gathering information | web_security | ar | intermediate | capec | kwcyber_000061 |
How does Interception attack work? | Attack Analysis | Technical analysis of Interception (CAPEC-117): An adversary monitors data streams to or from the target for information gathering purposes. This attack may be undertaken to solely gather sensitive information or to support a further attack against the target. This attack pattern can involve sniffing network traffic as well as other types of data streams (e.g. radio). The adversary can attempt to initiate the establishment of a data stream or passively observe the communications as they unfold. In all variants of this attack, the adversary is not the intended recipient of the data stream. In contrast to other means of gathering information | web_security | en | advanced | capec | kwcyber_000062 |
What is Choosing Message Identifier (CAPEC-12) attack pattern? | CAPEC | Choosing Message Identifier (CAPEC-12): This pattern of attack is defined by the selection of messages distributed via multicast or public information channels that are intended for another client by determining the parameter value assigned to that client. This attack allows the adversary to gain access to potentially privileged information, and to possibly perpetrate other attacks through the distribution means by impersonation. If the channel/message being manipulated is an input rather than output mechanism for the system, (such as a command bus), this style of attack could be used to change the adversary's identifier to more a p | web_security | en | intermediate | capec | kwcyber_000063 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Choosing Message Identifier (CAPEC-12)ุ | CAPEC | ูู
ุท ุงููุฌูู
Choosing Message Identifier (CAPEC-12): This pattern of attack is defined by the selection of messages distributed via multicast or public information channels that are intended for another client by determining the parameter value assigned to that client. This attack allows the adversary to gain access to potentially privileged information, and to possibly perpetrate other attacks through the distribution means by impersonation. If the channel/message being manipulated is an input rather than output mechanism for the system, (such as a command bus), this style of attack could be used to change the adversary's identifier to more a p | web_security | ar | intermediate | capec | kwcyber_000064 |
How does Choosing Message Identifier attack work? | Attack Analysis | Technical analysis of Choosing Message Identifier (CAPEC-12): This pattern of attack is defined by the selection of messages distributed via multicast or public information channels that are intended for another client by determining the parameter value assigned to that client. This attack allows the adversary to gain access to potentially privileged information, and to possibly perpetrate other attacks through the distribution means by impersonation. If the channel/message being manipulated is an input rather than output mechanism for the system, (such as a command bus), this style of attack could be used to change the adversary's identifier to more a p | web_security | en | advanced | capec | kwcyber_000065 |
What is Double Encoding (CAPEC-120) attack pattern? | CAPEC | Double Encoding (CAPEC-120): The adversary utilizes a repeating of the encoding process for a set of characters (that is, character encoding a character encoding of a character) to obfuscate the payload of a particular request. This may allow the adversary to bypass filters that attempt to detect illegal characters or strings, such as those that might be used in traversal or injection attacks. Filters may be able to catch illegal encoded strings, but may not catch doubly encoded strings. For example, a dot (.), often used in path traversal attacks and therefore often blocked by filters, could be URL encoded as %2E. Howeve | web_security | en | intermediate | capec | kwcyber_000066 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Double Encoding (CAPEC-120)ุ | CAPEC | ูู
ุท ุงููุฌูู
Double Encoding (CAPEC-120): The adversary utilizes a repeating of the encoding process for a set of characters (that is, character encoding a character encoding of a character) to obfuscate the payload of a particular request. This may allow the adversary to bypass filters that attempt to detect illegal characters or strings, such as those that might be used in traversal or injection attacks. Filters may be able to catch illegal encoded strings, but may not catch doubly encoded strings. For example, a dot (.), often used in path traversal attacks and therefore often blocked by filters, could be URL encoded as %2E. Howeve | web_security | ar | intermediate | capec | kwcyber_000067 |
How does Double Encoding attack work? | Attack Analysis | Technical analysis of Double Encoding (CAPEC-120): The adversary utilizes a repeating of the encoding process for a set of characters (that is, character encoding a character encoding of a character) to obfuscate the payload of a particular request. This may allow the adversary to bypass filters that attempt to detect illegal characters or strings, such as those that might be used in traversal or injection attacks. Filters may be able to catch illegal encoded strings, but may not catch doubly encoded strings. For example, a dot (.), often used in path traversal attacks and therefore often blocked by filters, could be URL encoded as %2E. Howeve | web_security | en | advanced | capec | kwcyber_000068 |
What is Exploit Non-Production Interfaces (CAPEC-121) attack pattern? | CAPEC | Exploit Non-Production Interfaces (CAPEC-121): <xhtml:p>An adversary exploits a sample, demonstration, test, or debug interface that is unintentionally enabled on a production system, with the goal of gleaning information or leveraging functionality that would otherwise be unavailable.</xhtml:p> | web_security | en | intermediate | capec | kwcyber_000069 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Exploit Non-Production Interfaces (CAPEC-121)ุ | CAPEC | ูู
ุท ุงููุฌูู
Exploit Non-Production Interfaces (CAPEC-121): <xhtml:p>An adversary exploits a sample, demonstration, test, or debug interface that is unintentionally enabled on a production system, with the goal of gleaning information or leveraging functionality that would otherwise be unavailable.</xhtml:p> | web_security | ar | intermediate | capec | kwcyber_000070 |
How does Exploit Non-Production Interfaces attack work? | Attack Analysis | Technical analysis of Exploit Non-Production Interfaces (CAPEC-121): <xhtml:p>An adversary exploits a sample, demonstration, test, or debug interface that is unintentionally enabled on a production system, with the goal of gleaning information or leveraging functionality that would otherwise be unavailable.</xhtml:p> | web_security | en | advanced | capec | kwcyber_000071 |
What is Privilege Abuse (CAPEC-122) attack pattern? | CAPEC | Privilege Abuse (CAPEC-122): An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-privileged accounts. Access to sensitive information and functionality must be controlled to ensure that only authorized users are able to access these resources. | web_security | en | intermediate | capec | kwcyber_000072 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Privilege Abuse (CAPEC-122)ุ | CAPEC | ูู
ุท ุงููุฌูู
Privilege Abuse (CAPEC-122): An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-privileged accounts. Access to sensitive information and functionality must be controlled to ensure that only authorized users are able to access these resources. | web_security | ar | intermediate | capec | kwcyber_000073 |
How does Privilege Abuse attack work? | Attack Analysis | Technical analysis of Privilege Abuse (CAPEC-122): An adversary is able to exploit features of the target that should be reserved for privileged users or administrators but are exposed to use by lower or non-privileged accounts. Access to sensitive information and functionality must be controlled to ensure that only authorized users are able to access these resources. | web_security | en | advanced | capec | kwcyber_000074 |
What is Buffer Manipulation (CAPEC-123) attack pattern? | CAPEC | Buffer Manipulation (CAPEC-123): An adversary manipulates an application's interaction with a buffer in an attempt to read or modify data they shouldn't have access to. Buffer attacks are distinguished in that it is the buffer space itself that is the target of the attack rather than any code responsible for interpreting the content of the buffer. In virtually all buffer attacks the content that is placed in the buffer is immaterial. Instead, most buffer attacks involve retrieving or providing more input than can be stored in the allocated buffer, resulting in the reading or overwriting of other unintended program memory. | web_security | en | intermediate | capec | kwcyber_000075 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Buffer Manipulation (CAPEC-123)ุ | CAPEC | ูู
ุท ุงููุฌูู
Buffer Manipulation (CAPEC-123): An adversary manipulates an application's interaction with a buffer in an attempt to read or modify data they shouldn't have access to. Buffer attacks are distinguished in that it is the buffer space itself that is the target of the attack rather than any code responsible for interpreting the content of the buffer. In virtually all buffer attacks the content that is placed in the buffer is immaterial. Instead, most buffer attacks involve retrieving or providing more input than can be stored in the allocated buffer, resulting in the reading or overwriting of other unintended program memory. | web_security | ar | intermediate | capec | kwcyber_000076 |
How does Buffer Manipulation attack work? | Attack Analysis | Technical analysis of Buffer Manipulation (CAPEC-123): An adversary manipulates an application's interaction with a buffer in an attempt to read or modify data they shouldn't have access to. Buffer attacks are distinguished in that it is the buffer space itself that is the target of the attack rather than any code responsible for interpreting the content of the buffer. In virtually all buffer attacks the content that is placed in the buffer is immaterial. Instead, most buffer attacks involve retrieving or providing more input than can be stored in the allocated buffer, resulting in the reading or overwriting of other unintended program memory. | web_security | en | advanced | capec | kwcyber_000077 |
What is Shared Resource Manipulation (CAPEC-124) attack pattern? | CAPEC | Shared Resource Manipulation (CAPEC-124): An adversary exploits a resource shared between multiple applications, an application pool or hardware pin multiplexing to affect behavior. Resources may be shared between multiple applications or between multiple threads of a single application. Resource sharing is usually accomplished through mutual access to a single memory location or multiplexed hardware pins. If an adversary can manipulate this shared resource (usually by co-opting one of the applications or threads) the other applications or threads using the shared resource will often continue to trust the validity of the compromised s | web_security | en | intermediate | capec | kwcyber_000078 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Shared Resource Manipulation (CAPEC-124)ุ | CAPEC | ูู
ุท ุงููุฌูู
Shared Resource Manipulation (CAPEC-124): An adversary exploits a resource shared between multiple applications, an application pool or hardware pin multiplexing to affect behavior. Resources may be shared between multiple applications or between multiple threads of a single application. Resource sharing is usually accomplished through mutual access to a single memory location or multiplexed hardware pins. If an adversary can manipulate this shared resource (usually by co-opting one of the applications or threads) the other applications or threads using the shared resource will often continue to trust the validity of the compromised s | web_security | ar | intermediate | capec | kwcyber_000079 |
How does Shared Resource Manipulation attack work? | Attack Analysis | Technical analysis of Shared Resource Manipulation (CAPEC-124): An adversary exploits a resource shared between multiple applications, an application pool or hardware pin multiplexing to affect behavior. Resources may be shared between multiple applications or between multiple threads of a single application. Resource sharing is usually accomplished through mutual access to a single memory location or multiplexed hardware pins. If an adversary can manipulate this shared resource (usually by co-opting one of the applications or threads) the other applications or threads using the shared resource will often continue to trust the validity of the compromised s | web_security | en | advanced | capec | kwcyber_000080 |
What is Flooding (CAPEC-125) attack pattern? | CAPEC | Flooding (CAPEC-125): An adversary consumes the resources of a target by rapidly engaging in a large number of interactions with the target. This type of attack generally exposes a weakness in rate limiting or flow. When successful this attack prevents legitimate users from accessing the service and can cause the target to crash. This attack differs from resource depletion through leaks or allocations in that the latter attacks do not rely on the volume of requests made to the target but instead focus on manipulation of the target's operations. The key factor in a flooding attack is the number of requests the adver | web_security | en | intermediate | capec | kwcyber_000081 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Flooding (CAPEC-125)ุ | CAPEC | ูู
ุท ุงููุฌูู
Flooding (CAPEC-125): An adversary consumes the resources of a target by rapidly engaging in a large number of interactions with the target. This type of attack generally exposes a weakness in rate limiting or flow. When successful this attack prevents legitimate users from accessing the service and can cause the target to crash. This attack differs from resource depletion through leaks or allocations in that the latter attacks do not rely on the volume of requests made to the target but instead focus on manipulation of the target's operations. The key factor in a flooding attack is the number of requests the adver | web_security | ar | intermediate | capec | kwcyber_000082 |
How does Flooding attack work? | Attack Analysis | Technical analysis of Flooding (CAPEC-125): An adversary consumes the resources of a target by rapidly engaging in a large number of interactions with the target. This type of attack generally exposes a weakness in rate limiting or flow. When successful this attack prevents legitimate users from accessing the service and can cause the target to crash. This attack differs from resource depletion through leaks or allocations in that the latter attacks do not rely on the volume of requests made to the target but instead focus on manipulation of the target's operations. The key factor in a flooding attack is the number of requests the adver | web_security | en | advanced | capec | kwcyber_000083 |
What is Path Traversal (CAPEC-126) attack pattern? | CAPEC | Path Traversal (CAPEC-126): An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attac | web_security | en | intermediate | capec | kwcyber_000084 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Path Traversal (CAPEC-126)ุ | CAPEC | ูู
ุท ุงููุฌูู
Path Traversal (CAPEC-126): An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attac | web_security | ar | intermediate | capec | kwcyber_000085 |
How does Path Traversal attack work? | Attack Analysis | Technical analysis of Path Traversal (CAPEC-126): An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attac | web_security | en | advanced | capec | kwcyber_000086 |
What is Directory Indexing (CAPEC-127) attack pattern? | CAPEC | Directory Indexing (CAPEC-127): An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, | web_security | en | intermediate | capec | kwcyber_000087 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Directory Indexing (CAPEC-127)ุ | CAPEC | ูู
ุท ุงููุฌูู
Directory Indexing (CAPEC-127): An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, | web_security | ar | intermediate | capec | kwcyber_000088 |
How does Directory Indexing attack work? | Attack Analysis | Technical analysis of Directory Indexing (CAPEC-127): An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, | web_security | en | advanced | capec | kwcyber_000089 |
What is Integer Attacks (CAPEC-128) attack pattern? | CAPEC | Integer Attacks (CAPEC-128): An attacker takes advantage of the structure of integer variables to cause these variables to assume values that are not expected by an application. For example, adding one to the largest positive integer in a signed integer variable results in a negative number. Negative numbers may be illegal in an application and the application may prevent an attacker from providing them directly, but the application may not consider that adding two positive numbers can create a negative number do to the structure of integer storage formats. | web_security | en | intermediate | capec | kwcyber_000090 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Integer Attacks (CAPEC-128)ุ | CAPEC | ูู
ุท ุงููุฌูู
Integer Attacks (CAPEC-128): An attacker takes advantage of the structure of integer variables to cause these variables to assume values that are not expected by an application. For example, adding one to the largest positive integer in a signed integer variable results in a negative number. Negative numbers may be illegal in an application and the application may prevent an attacker from providing them directly, but the application may not consider that adding two positive numbers can create a negative number do to the structure of integer storage formats. | web_security | ar | intermediate | capec | kwcyber_000091 |
How does Integer Attacks attack work? | Attack Analysis | Technical analysis of Integer Attacks (CAPEC-128): An attacker takes advantage of the structure of integer variables to cause these variables to assume values that are not expected by an application. For example, adding one to the largest positive integer in a signed integer variable results in a negative number. Negative numbers may be illegal in an application and the application may prevent an attacker from providing them directly, but the application may not consider that adding two positive numbers can create a negative number do to the structure of integer storage formats. | web_security | en | advanced | capec | kwcyber_000092 |
What is Pointer Manipulation (CAPEC-129) attack pattern? | CAPEC | Pointer Manipulation (CAPEC-129): This attack pattern involves an adversary manipulating a pointer within a target application resulting in the application accessing an unintended memory location. This can result in the crashing of the application or, for certain pointer values, access to data that would not normally be possible or the execution of arbitrary code. Since pointers are simply integer variables, Integer Attacks may often be used in Pointer Attacks. | web_security | en | intermediate | capec | kwcyber_000093 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Pointer Manipulation (CAPEC-129)ุ | CAPEC | ูู
ุท ุงููุฌูู
Pointer Manipulation (CAPEC-129): This attack pattern involves an adversary manipulating a pointer within a target application resulting in the application accessing an unintended memory location. This can result in the crashing of the application or, for certain pointer values, access to data that would not normally be possible or the execution of arbitrary code. Since pointers are simply integer variables, Integer Attacks may often be used in Pointer Attacks. | web_security | ar | intermediate | capec | kwcyber_000094 |
How does Pointer Manipulation attack work? | Attack Analysis | Technical analysis of Pointer Manipulation (CAPEC-129): This attack pattern involves an adversary manipulating a pointer within a target application resulting in the application accessing an unintended memory location. This can result in the crashing of the application or, for certain pointer values, access to data that would not normally be possible or the execution of arbitrary code. Since pointers are simply integer variables, Integer Attacks may often be used in Pointer Attacks. | web_security | en | advanced | capec | kwcyber_000095 |
What is Subverting Environment Variable Values (CAPEC-13) attack pattern? | CAPEC | Subverting Environment Variable Values (CAPEC-13): The adversary directly or indirectly modifies environment variables used by or controlling the target software. The adversary's goal is to cause the target software to deviate from its expected operation in a manner that benefits the adversary. | web_security | en | intermediate | capec | kwcyber_000096 |
ู
ุง ูู ูู
ุท ุงููุฌูู
Subverting Environment Variable Values (CAPEC-13)ุ | CAPEC | ูู
ุท ุงููุฌูู
Subverting Environment Variable Values (CAPEC-13): The adversary directly or indirectly modifies environment variables used by or controlling the target software. The adversary's goal is to cause the target software to deviate from its expected operation in a manner that benefits the adversary. | web_security | ar | intermediate | capec | kwcyber_000097 |
How does Subverting Environment Variable Values attack work? | Attack Analysis | Technical analysis of Subverting Environment Variable Values (CAPEC-13): The adversary directly or indirectly modifies environment variables used by or controlling the target software. The adversary's goal is to cause the target software to deviate from its expected operation in a manner that benefits the adversary. | web_security | en | advanced | capec | kwcyber_000098 |
What is Excessive Allocation (CAPEC-130) attack pattern? | CAPEC | Excessive Allocation (CAPEC-130): An adversary causes the target to allocate excessive resources to servicing the attackers' request, thereby reducing the resources available for legitimate services and degrading or denying services. Usually, this attack focuses on memory allocation, but any finite resource on the target could be the attacked, including bandwidth, processing cycles, or other resources. This attack does not attempt to force this allocation through a large number of requests (that would be Resource Depletion through Flooding) but instead uses one or a small number of requests that are carefully formatted to forc | web_security | en | intermediate | capec | kwcyber_000099 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.