CWE-16
OWASP 2013-A5
OWASP 2017-A6

ASP.NET Cookieless Authentication Is Enabled

Severity:
Medium
Summary

Invicti detected that the cookieless authentication is enabled inside of the ASP.NET application.

Impact

When an ASP.NET application is configured to use cookieless authentication, it stores the authentication token in the page URLs rather than a cookie. This makes it easier for an attacker to perform session hijacking.

Remediation
Required Skills for Successful Exploitation
Actions To Take

Cookieless Forms Authentication is enabled within the machine.config file or the web.config file of your application by setting the new cookieless attribute. To disable cookieless authentication, set cookieless attribute to “UseCookies”.

<configuration>

<system.web>

<authentication mode="Forms">

<forms name=".ASPXAUTH"

loginUrl="login.aspx"

protection="All"

timeout="30"

path="/"

requireSSL="false"

slidingExpiration="true"

defaultUrl="default.aspx"

cookieless="UseCookies" />

</authentication>

</system.web>

</configuration>

Classifications
Vulnerability Index

You can search and find all vulnerabilities

Select Vulnerability
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Featured resources

Blog

Strengthening enterprise application security: Invicti acquires Kondukto

Blog

Modern AppSec KPIs: Moving from scan counts to real risk reduction

Blog

Friends don’t let friends shift left: Shift smarter with DAST-first AppSec

Blog

Vibe talking: Dan Murphy on the promises, pitfalls, and insecurities of vibe coding

Blog

What lies ahead for CMS.

Blog

How to integrate CMS with other tools.

Blog

Improve user experience through CMS.

Blog

How CMS can benefit e-commerce.

Blog

Stay updated on CMS trends.

Blog

Tips for improving CMS performance.

Blog

Learn how to secure your CMS.

Blog

Explore the advantages of CMS.

Blog

A comprehensive guide to CMS.

Build your resistance to threats. And save hundreds of hours each month.