Vulnerability Guide
This section lists all vulnerabilities (issues) that can be detected by Bright and provides detailed information about each of them.
Test Name | Description | Detectable Vulnerabilities |
|---|---|---|
Amazon S3 Bucket Takeover | Tests for S3 buckets that no longer exist to prevent data breaches and malware distribution | |
Broken JWT Authentication | Tests for secure implementation of JSON Web Token (JWT) in the application | |
Broken SAML Authentication | Tests for secure implementation of SAML authentication in the application | |
Brute Force Login | Tests for the availability of commonly used credentials | |
Business Constraint Bypass | Tests if the limitation of the number of retrievable items via an API call is configured properly | |
Cross-Site Scripting (XSS) | Tests if various application DOM parameters are vulnerable to JavaScript injections | |
Common Files Exposure | Tests if common files that should not be accessible are accessible | |
Common Vulnerability Exposure (CVEs) | Tests for known third-party common vulnerability exposures | |
Cookie Security Check | Tests if the application uses and implements cookies with secure attributes | Sensitive Cookie in HTTPS Session Without Secure Attribute |
Cross-Site Request Forgery (CSRF) | Tests application forms for vulnerable cross-site filling and submitting | |
Cross-Site Scripting (XSS) | Tests if various application parameters are vulnerable to JavaScript injections | |
CSS Injection | Tests for weaknesses that could allow hackers to inject malicious Cascading Style Sheets (CSS) code | |
Default Login Location | Tests if login form location in the target application is easy to guess and accessible | |
Directory Listing | Tests if server-side directory listing is possible | |
Email Header Injection | Tests if it is possible to send emails to other addresses through the target application mailing server, which can lead to spam and phishing | |
Exposed AWS S3 Buckets Details | Tests if exposed AWS S3 links lead to anonymous read access to the bucket | |
Exposed Database Details | Tests if exposed database connection strings are open to public connections | |
Excessive Data Exposure | Tests application for not screening sensitive information on the server side | |
Full Path Disclosure (FPD) | Tests if various application parameters are vulnerable to the exposure of errors that include full webroot path | |
GraphQL introspection | GraphQL data availability test for queries coming from external IP-address | |
Headers Security Check | Tests for proper Security Headers configuration | |
HTML Injection | Tests if various application parameters are vulnerable to HTML injection | |
iFrame Injection | Tests for frame injection attacks evaluate the embedding of deceptive elements on legitimate websites, tricking users into unintended interactions that lead to unauthorized actions, data theft, or malicious activities. | |
Improper Assets Management | Tests if older or development versions of API endpoints are exposed and can be used to get unauthorized access to data and privileges | |
Insecure HTTP Method | Tests enumeration of possible HTTP methods for vulnerabilities | |
Insecure TLS Configuration | Tests SSL/TLS ciphers and configurations for vulnerabilities | |
Known JavaScript Vulnerabilities | Tests for known JavaScript component vulnerabilities | |
Lack of Resources and Rate Limiting | Tests all API endpoints for rate-limiting or resource exhaustion protection in place. | |
LDAP Injection | Tests if various application parameters are vulnerable to unauthorized LDAP access | |
Local File Inclusion (LFI) | Tests if various application parameters are vulnerable to loading of unauthorized local system resources | |
Mass Assignment | Tests if it is possible to create requests with additional parameters to gain privilege escalation | |
OS Command Injection | Tests if various application parameters are vulnerable to Operation System (OS) commands injection | |
Prompt Injection | Tests for prompt injections assess the manipulation of LLMs through crafted prompts, which can result in unintended actions and security vulnerabilities like data leaks and unauthorized access. | |
Prototype Pollution | Tests if it is possible to inject properties into existing JavaScript objects | |
Remote File Inclusion (RFI) | Tests if various application parameters are vulnerable to loading of unauthorized remote system resources | |
Secret Tokens Leak | Tests for exposure of secret API tokens or keys in the target application | |
Server Side Template Injection (SSTI) | Tests if various application parameters are vulnerable to server-side code execution | |
Server Side Request Forgery (SSRF) | Tests if various application parameters are vulnerable to internal resources access | |
SQL Injection (SQLI) | SQL Injection tests vulnerable parameters for SQL database access | |
Unrestricted File Upload | Tests if file upload mechanisms are validated properly and denies upload of malicious content | |
Unsafe Date Range | Tests if date ranges are set and validated properly | |
Unsafe Redirect | Tests if various application parameters are vulnerable to the injection of a malicious link that can redirect a user without validation | |
User ID Enumeration | Tests if it is possible to collect valid user ID data by interacting with the target application | |
Version Control System Data Leak | Tests if it is possible to access Version Control System (VCS) resources | |
XML External Entity Injection | Tests if various XML parameters are vulnerable to XML parsing of unauthorized external entities |
Updated 16 days ago