Knowledge Base - Issues
Our knowledge-base provides a comprehensive collection of information on vulnerabilities related to cyber security.Ability to Forge Requests is a vulnerability in Web and API applications that can allow attackers to send requests with forged data to the application. This vulnerability is classified under CWE-502 (Deserialization of Untrusted Data) in the Common Weakness Enumeration (CWE) directory and is identified as a Business Logic vulnerability...
Account Provisioning is an IT vulnerability of the category Identity Management, which occurs in Web and API. This vulnerability involves the ability to create and manage user accounts, allowing malicious actors to gain unauthorized access. According to the Common Weakness Enumeration (CWE) directory, Account Provisioning is a vulnerability that involves...
Admin interface identified is a vulnerability related to information gathering. It is categorized under CWE-200 and is classified as an ‘Incomplete Information’ type vulnerability. This vulnerability arises when an attacker is able to identify and access the administrative interface of a web application or API without the user’s authorization. This...
Ajax request header manipulation (CWE-20) is a type of client side vulnerability in web and API applications that can be exploited by manipulating the request headers sent from the client. This attack can be used to gain access to restricted resources, bypass authentication or authorization mechanisms, or modify data stored...
ASP.NET debugging enabled is a configuration management vulnerability (CWE-534) that occurs in web and API applications. It occurs when ASP.NET debugging is enabled in a production environment, allowing attackers to access debugging information and potentially exploit the web application. According to the OWASP Testing Guide, "Debugging information can provide an...
ASP.NET tracing enabled is a vulnerability in web and API applications that can allow attackers to gain access to sensitive information stored in the application. This vulnerability is described in the Common Weakness Enumeration (CWE) directory as CWE-611: Improper Restriction of Excessive Authentication Attempts. It can also be found in...
ASP.NET ViewState without MAC enabled is a cryptography vulnerability, classified under CWE-352, that occurs in web and API applications. It occurs when the application does not properly validate the ViewState data transmitted between the client and the server, enabling malicious users to tamper with the contents of the ViewState. This...
Authentication Bypass by Capture-replay is a class of vulnerability found in web and API applications that allows an attacker to bypass authentication mechanisms by replaying credentials or authentication tokens that were previously captured (CWE-287). The attack is usually executed by intercepting the authentication traffic via man-in-the-middle or by sniffing the...
Authentication Bypass by Spoofing is a type of vulnerability which occurs when an attacker is able to bypass the authentication process by providing false or incorrect credentials. This vulnerability is categorized under Authentication in the [Common Weakness Enumeration (CWE)](https://cwe.mitre.org/data/definitions/287.html) directory and is applicable to Web and API applications. It is...
Authentication Bypass Using an Alternate Path or Channel (CWE-287) is a vulnerability that can occur when authentication is not properly enforced, or when an alternate path or channel is used to bypass authentication. In web and API applications, this can occur when an attacker can gain access to an application...
Backdoors are authentication vulnerabilities that allow attackers to bypass authentication mechanisms and gain access to systems, applications, or other resources. This type of vulnerability is defined in the Common Weakness Enumeration (CWE) directory as CWE-798: Use of Hard-coded Credentials. It affects web and API applications as well as infrastructure components...
Backup file is an authorization vulnerability that occurs when an application does not properly restrict access to backup files, such as database backups. This type of vulnerability allows an attacker to gain access to sensitive data, such as passwords and personal information, which can be used to gain further access...
Base64-encoded data in parameter is a type of cryptography vulnerability that occurs in Web and API applications. According to Common Weakness Enumeration (CWE) directory, it is classified as CWE-344: Improper Insufficient Cryptographic Validation. This vulnerability is caused when an application fails to validate or restrict the unverified Base64- encoded data...
Browser Cache Weaknesses is a type of authentication vulnerability, commonly found in Web and API applications, as classified by the Common Weakness Enumeration (CWE) directory. This vulnerability occurs when a browser stores credentials and other sensitive information in the browser cache, and this information can be accessed by an attacker,...
Browser cross-site scripting filter disabled (CWE-79) is a configuration management vulnerability that falls under Web and API category. This vulnerability allows malicious code to be executed in the user’s browser, as the cross-site scripting filter is not enabled. According to the OWASP Testing Guide, cross-site scripting filters are used to...
Browser Storage is a type of Client Side Vulnerability (CWE-79) which permits unvalidated data to be stored on the browser. This vulnerability is most commonly found in web and API applications, where it can be exploited by a malicious attacker to extract sensitive user data, such as passwords, session tokens,...
Bypassing Authorization Schema is an authorization vulnerability that occurs in web and API applications. It is categorized under CWE-285 (Improper Authorization) in the Common Weakness Enumeration (CWE) directory. According to the Open Web Application Security Project (OWASP) Testing Guide, this type of attack occurs when an attacker manages to access...
Cacheable HTTPS response, CWE-315, occurs when a web server or API responds to an HTTPS request with a response that is marked as cacheable. This can lead to the response being stored in an unencrypted form, exposing sensitive data to anyone with access to the cache. According to the OWASP...
Circumvention of Work Flows, also known as CWE-20, is a type of Business Logic vulnerability which allows attackers to bypass established workflow procedures. This vulnerability can occur in both web-based and API-based applications. According to the Common Weakness Enumeration (CWE) directory, the vulnerability is defined as “the ability to bypass...
Cleartext storage of sensitive information in cookie is a vulnerability that occurs when an application stores sensitive information in a cookie without any encryption or hashing. This can make it easy for an attacker to access the stored information. This vulnerability is classified as CWE-312 and is listed in the...
Description
Cleartext submission of password is a vulnerability classified under CWE-259: Use of Hard-coded Password. It occurs when a password is transmitted in a non-encrypted form during authentication processes over an open network like the internet. This is a high risk vulnerability as unencrypted data can be easily intercepted by malicious...
Clickjacking (UI Redressing) is a type of attack that occurs when an attacker uses multiple transparent or opaque layers to deceive a user into clicking on a button or link on another page when they were expecting to click on the top level page. This attack can be used to...
Client-side HTTP parameter pollution (CWE-20) is a type of web application vulnerability that occurs when user-supplied parameters are used to manipulate the intended logic of a web application. The attacker can inject additional HTTP parameters into a single HTTP request, which can be used to manipulate the application's behaviour. By...
Description
Client-side JSON injection (DOM-based) is a type of vulnerability that occurs when a malicious user is able to inject JSON directly into a web page, usually through a browser, allowing malicious code to be executed within the browser. This vulnerability is categorized as a Client Side Vulnerability according to the...
Client-side Resource Manipulation (CWE-502) is one of the most critical client-side vulnerabilities that can occur in web and API applications. It is described in the [Common Weakness Enumeration (CWE)](https://cwe.mitre.org/data/definitions/502.html) directory as the ability to manipulate resources in the client-side before they are used by the application. This vulnerability can be...
Client-side SQL injection (DOM-based) is a type of injection attack that is classified as a Client Side Vulnerability (CWE-79). It occurs when a web application allows user-supplied input to be executed as part of a SQL query without proper validation or sanitization. According to the OWASP Testing Guide, DOM-based SQL...
Client-side template injection (CSTI) is a type of injection attack that occurs when user-supplied data is injected into a web template in a client-side context. This type of attack is particularly dangerous as it allows an attacker to inject malicious code into a web page that is then executed by...
Client-side URL Redirect, also known as Open Redirect, is a vulnerability that occurs when a web application accepts an user-controlled input that specifies a redirection to an external URL. This vulnerability is listed as CWE-601 in the Common Weakness Enumeration (CWE) directory and is categorized under Client Side Vulnerabilities. It...
Client-side XPath injection (DOM-based) is a type of security vulnerability which is classified under Client Side Vulnerabilities as per the Common Weakness Enumeration (CWE), and occurs in web and API applications. This is a type of injection attack where an attacker injects malicious XPath statements into a client's web page,...
Description
Content Sniffing not disabled is a Configuration Management vulnerability (CWE-943) that occurs in Web and API applications. It is a type of attack that attempts to exploit potential security flaws in web applications by exploiting the client's ability to interpret data sent from the server. Content Sniffing not disabled can...
Content type incorrectly stated, also known as CWE-200, is a type of vulnerability related to configuration management in web and API applications. It occurs when an application incorrectly states the content type of a response when the content type is not correctly given by the application. This can be dangerous...
Content type is not specified is a vulnerability that falls under the category of Configuration Management in the Common Weakness Enumeration (CWE) directory (CWE-20). This vulnerability occurs when there is no content type specified for data sent via Web and API requests. If a content type is not specified, the...
Cookie issued to parent domain is a web application vulnerability in the configuration management category (CWE-20). The vulnerability occurs when a cookie is issued to a parent domain, allowing the cookie to be accessed in the parent domain or other subdomains. This type of cookie injection can be used to...
Cookie manipulation (DOM-based) is a type of web application security vulnerability classified as a Client Side Vulnerability. This vulnerability occurs when web applications fail to properly validate the integrity of cookies, resulting in the ability to execute malicious code. According to the [Common Weakness Enumeration (CWE) directory, this vulnerability is...
Cookie Variable Exposed is a type of vulnerability commonly found in web and API applications. It occurs when data stored in a cookie is made available to an unauthorized user, allowing them to gain access to the application or system. This vulnerability is classified as an Authentication vulnerability in the...
Cookies Attributes is a vulnerability in Session Management, which is a subcategory of Web and API Security according to the Common Weakness Enumeration (CWE) directory. This vulnerability occurs when the server fails to properly set the attributes of the cookie. This can be due to a lack of proper configuration...
Credit card numbers disclosed is an authentication vulnerability (CWE-522) where credit card numbers, expiration dates, and CVV numbers are exposed during authentication. This vulnerability is commonly found in web applications and APIs (OWASP Testing Guide, V3.0). This type of vulnerability can be exploited with malicious intent, such as stealing credit...
Cross Site Flashing (CWE-959) is a vulnerability that allows attackers to inject malicious content into a vulnerable web or API application. It is a type of client-side vulnerability that occurs when a vulnerable application allows an attacker to inject malicious content into a web page or API call. The malicious...
Cross-Site Script Inclusion (CWE-832) is a type of Client Side Vulnerability which refers to the ability of an attacker to execute malicious scripts in a web application or API by exploiting the application's code or configurations. This type of attack is based on the fact that the scripts of a...
Cross Site Scripting (DOM-Based) is a type of client side vulnerability that is listed in the CWE Top 25 (2022) and is classified as CWE-79. It is a type of injection attack that allows an attacker to execute malicious JavaScript on a web page or in an API. The attacker...
Cross-domain POST is a type of IT vulnerability which falls under the category of Configuration Management. This vulnerability is primarily found in web applications and APIs, and is defined as the ability to send a request from one domain to another, which is often done by malicious actors. This type...
Cross-domain Referer leakage is an authorization vulnerability that occurs when web applications fail to properly validate the HTTP Referer header. This allows attackers to bypass the same origin policy and access resources in another domain. This vulnerability is classified as CWE-352 (Cross-Site Request Forgery (CSRF)) in the Common Weakness Enumeration...
Cross-domain script include is a type of authentication vulnerability that occurs when a web application allows malicious scripts to be included from a different domain. This type of vulnerability can allow attackers to bypass access controls, such as the same-origin policy, allowing them to access sensitive data from the victim’s...
Cross-origin resource sharing (CORS) is a vulnerability that occurs when a malicious website is allowed to access resources in a different domain. It is classified as a client-side vulnerability because it is the client's browser that is responsible for controlling access to resources. CORS is classified as CWE-918 in the...
A _Cross-Origin Resource Sharing (CORS)_ policy controls whether and how content running on other domains can interact with the domain that publishes the policy. The policy is granular and can apply per-request access controls based on the URL and other characteristics of the request.
# Risk
The common exploitation scenarios can be...
Cross-origin resource sharing (CORS) is a browser mechanism which enables controlled access to resources located outside of a given domain. It extends and adds flexibility to the same-origin policy (SOP). It also provides potential for cross-domain based attacks, if a website's CORS policy is poorly configured and implemented. CORS is...
A _Cross-Origin Resource Sharing (CORS)_ policy controls whether and how content running on other domains can interact with the domain that publishes the policy. The policy is granular and can apply per-request access controls based on the URL and other characteristics of the request.
# Risk
If a site allows interaction...
Cross-Site Request Forgery (CSRF) is an attack vector that exploits the trust a website has for a user. It is a type of attack classified as a client-side attack, where an attacker can send malicious requests in the name of the target user without their knowledge. According to Common Weakness...
CSS Injection (reflected) is an input validation vulnerability that occurs when an application does not properly validate input from a web or API user. This type of attack allows malicious code to be injected into a web page such that it is reflected back to the user when it is...
CSS injection (stored) is a type of input validation vulnerability which occurs when a web application stores user-supplied data in a web page without properly validating or encoding it, which allows malicious users to inject arbitrary CSS code into the page. This type of vulnerability is classified in the Common...
Showing entries 1 to 50 of 254 entries.