• Open Redirects: A Forgotten Vulnerability? • In 2010, OWASP added “Unvalidated Redirects and Forwards” to its Top 10 list and merged it into “Sensitive Data Exposure” in 2013 [owasp1] [owasp2]. • Open redirects are often overlooked, and their impact is not always well understood. • At first, it does not look like a big deal. • The user is receiving a 3xx status code and is being redirected to another URL. • That target URL should handle all authentication and access control, regardless of where the data originated.

Article Summaries:

  • Open Redirects: A Forgotten Vulnerability? A recent report highlights a resurgence of open‑redirect attacks, a flaw long listed in OWASP’s Top 10 but often overlooked. Honeypots detected a spike in requests to redirect endpoints (e.g., /continue?url=..., /redirect?url=...) in February, all originating mainly from IP 89.248.168.239, a host in the Seychelles known as a “bulletproof” provider. The vulnerability remains critical because it can facilitate phishing and subvert OAuth redirect URLs, which rely on strict allow‑listing. Security experts now recommend blocking traffic from AS202425 to mitigate the growing threat.
  • Open Redirects: A Forgotten Vulnerability? In 2010, OWASP added “Unvalidated Redirects and Forwards” to its Top 10 list and merged it into “Sensitive Data Exposure” in 2013 [owasp1] [owasp2]. Open redirects are often overlooked, and their impact is not always well understood. At first, it does not look like a big deal. The user is receiving a 3xx status code and is being redirected to another URL. That target URL should handle all authentication and access control, regardless of where the data originated. Historically, one of the main concerns was phishing. A user clicks on a link to a trusted

Sources: