Open redirect in path

Tests for open redirect vulnerability by injecting evil.com into URL path, ensuring secure redirection and protection against malicious redirects.

Security Misconfiguration (SM)

Impact of the vulnerability

This behavior can be leveraged to facilitate phishing attacks against users of the application.

How this template works

APIs Selection

The template uses API selection filters to specify the criteria for selecting the API requests to be executed. In this case, the filters are based on the response code and URL. The filter checks if the response code is equal to 302 (redirect) and if the URL matches a regular expression pattern. It also extracts a variable called "urlVar" from the URL.

Execute request

The template defines a single request to be executed. It modifies the URL by replacing the protocol (http or https) with "http://evil.com" using a regular expression. It then disables following redirects for this request.

Validation

After executing the request, the template validates the response. It checks if the response code is equal to 302 (redirect) and if the response headers contain the key "location" with a value that contains either "evil.com". This validation ensures that the request was redirected to a URL containing "evil.com", indicating a potential open redirect vulnerability.

Frequently asked questions

What is the purpose of injecting 'evil.com' into the URL path in this test

How does this test help in detecting and mitigating open redirect vulnerabilities

What are the potential risks associated with open redirect vulnerabilities

Why is it important to ensure robust protection against open redirect vulnerabilities

What category and severity level does this vulnerability fall under

What are some references or resources that provide more information about open redirect vulnerabilities

Loved by security teams!

"We are absolutely thrilled with the testing feature of Akto. We have used it on our graphQL endpoints and it performs flawlessly identifying common API security issues. It's truly a game-changer and we highly recommend Akto to anyone looking to effortlessly secure their API endpoints. With a user-friendly interface, it's the perfect solution for anyone looking to embrace custom rules with context to reduce false positives."

Security team,

Loom

Security team,

Loom

Security team,

Loom

"The text editor in Akto is absolutely remarkable. Its user-friendly YAML format strikes the perfect balance between simplicity and power. With intuitive features like 'API selection filter', 'Execute', Validate' creating test rules becomes incredibly easy. Akto's test editor is a game-changer, enabling seamless creation of highly personalized and effective tests that could meet the needs of any modern day organization. "

Security team,

Rippling

Security team,

Rippling

Security team,

Rippling

Explore other tests

eSMTP - Config Discovery

Nginx - Git Configuration Exposure

Laravel - Sensitive Information Disclosure

Docker Container - Misconfiguration Exposure

Msmtp - Config Exposure

Parameters.yml - File Discovery

Mongo Express - Unauthenticated Access

Apache Airflow Configuration Exposure

Dockerrun AWS Configuration Exposure

Apache Config file disclosure

Appspec Yml Disclosure

CGI script environment variable

Learn more:

Content

4 min read

Introducing AktoGPT to secure APIs

Content

10 min read

What's changed in OWASP API Security Top 10 2023 Release Candidate from 2019?

Suggest API security tests

We're actively building the test library. Suggest a test! If we like your suggestion, you will see it in the library in few days.