Netsparker detected that
Elmah.axd is accessible remotely, and Elmah has been used for error logging.
This vulnerability can cause highly sensitive data leaks on current sessions.
web.configfile to disable remote access to the Elmah.axd error log:
<elmah> <security allowRemoteAccess="no"/> </elmah>You can also use ASP.NET's own authorization mechanism to protect your Elmah.axd error log from attackers. The following configuration makes your Elmah.axd error log viewable by only authorized
<configuration> <location path="elmah.axd"> <system.web> <authorization> <allow roles="Administrators"/> <deny users="*"/> </authorization> </system.web> </location> </configuration>