All vulnerabilities

The response contains headers which might leak sensitive information.

The endpoint appears to accept requests with TRACK HTTP Method. The original request was replayed by replacing the method value with TRACK. The application responded with 2XX success code.

The endpoint appears to accept requests with TRACE HTTP Method. The original request was replayed by replacing the method value with TRACE. The application responded with 2XX success code.

Attacker can obtain information about the software version and other identifying details of the server software running on a remote system.

Attacker can obtain information about the software version and other identifying details of the server software running on a remote system.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing XML upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing PDF upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with localhost/admin in an encoded format. The application responded with 2XX success code and also gave out admin-related details.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with localhost/admin. The make-127-0-0-1-rr.1u.ms/admin which redirects to localhost/admin.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with localhost/admin. The application responded with 2XX success code and also gave out admin-related details.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing image upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing file parameter with sensitive file path. The application responded with 2XX success code and also gave out sensitive AWS information in response.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing CSV upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with metadata endpoint provided by AWS. The application responded with 2XX success code and also gave out sensitive AWS information in response.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with metadata endpoint provided by AWS in enclosed alphanumerics. The application responded with 2XX success code and also gave out sensitive AWS information in response.

Vulnerability assessment by replacing the CSRF token with an invalid one

Assessing the system's vulnerability by removing the CSRF token to determine if unauthorized actions can be performed.

Many authentication mechanisms only limit access to the most common HTTP methods, thus allowing unauthorized access to restricted resources by other HTTP methods.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with some of the popular ports. The application responded with 2XX success code indicating that the port is open.

Attacker can access resources of any user by introducing multiple parameters with same name.

Quite often, APIs do not impose any restrictions on the size or number of resources that can be requested by the user.

An attacker can construct a URL within the application that causes a redirection to an arbitrary external domain.

Attacker can access resources of any user by changing the auth token in request and using older version of an API

API doesn't validate the authenticity of token. Attacker can remove the auth token and access the endpoint.

The response does not contain some HTTP security headers.

The endpoint appears to be vulnerable to Mass Assignment attack. The original request was replayed by adding role with admin permissions in request body. The application responded with 2XX success code in response.

The endpoint appears to be vulnerable to Mass Assignment attack. The original request was replayed by modifyinh role param in request body. The application responded with 2XX success code in response.

The endpoint appears to be vulnerable to Mass Assignment attack. The original request was replayed by modifying admin param in request body. The application responded with 2XX success code in response.

The endpoint appears to be vulnerable to Mass Assignment attack. The original request was replayed by changing account value in request body. The application responded with 2XX success code in response.

Since NONE Algorithm JWT is accepted by the server the attacker can tamper with the payload of JWT and access protected resources.

Since server is not validating the JWT signature the attacker can tamper with the payload of JWT and access protected resources

The error response contains information which may help in more sophisticated attacks

Many authentication mechanisms only limit access to the most common HTTP methods, thus allowing unauthorized access to restricted resources by other HTTP methods.

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with popular sensitive file paths. The application responded with 2XX success code and also gave out details of these files.

The error response contains information related to urls which may help in more sophisticated attacks

This vulnerability can enable attackers to inject malicious code into the application or cause it to malfunction.

Hackers trick users to log into their account by forging requests, exploiting server authentication.

Validates the Cross-Origin Resource Sharing (CORS) whitelist, ensuring only authorized origins are included, enhancing application security.

"Detects misconfigured Cross-Origin Resource Sharing (CORS) settings by checking for invalid origin values, preventing unauthorized access."

Attacker can access resources of any user by changing the auth token in request.

Attacker can access resources of any user by adding user_id in URL.

Testing vulnerability by injecting malicious scripts in filenames to bypass security measures and execute unauthorized code.

Testing vulnerability by injecting malicious scripts in filenames to bypass security measures and execute unauthorized code.

Injecting malicious content into a web url to mislead users.

Detection of Struts OGNL console enabled misconfiguration, which can lead to remote code execution vulnerabilities.

Struts debug mode enabled misconfiguration can expose sensitive information, potentially leading to security vulnerabilities.

Spring Boot Thread Dump Actuator Exposed Misconfiguration

Spring Boot Http Trace Actuator Exposed Misconfiguration.

Spring Boot Environment Actuator Exposed Misconfiguration.

Spring Boot Configuration Properties Actuator Exposed Misconfiguration.

Spring Boot Beans Actuator Exposed Misconfiguration.

This test detects vulnerabilities in web applications, ensuring proper session management and protection against attacks.

Fuzzing vulnerable payloads in request body and query params to assess Server-Side Template Injection vulnerability.

Fuzzing vulnerable payloads in request body and query params to assess Server-Side Template Injection vulnerability.