Wednesday, February 04, 2004 - Posts
The Open Web Application Security Project (OWASP) has released an interesting ranking of the Top 10 Vulnerabilities in Web Applications. This is a list of vulnerabilities that require to be checked immediately because they are actively targeted by attackers. Belowe there's the list published by the OWASP... check it and make attention in your applications...
Top Vulnerabilities in Web Applications |
A1 | Unvalidated Input | Information from web requests is not validated before being used by a web application. Attackers can use these flaws to attack backend components through a web application. |
A2 | Broken Access Control | Restrictions on what authenticated users are allowed to do are not properly enforced. Attackers can exploit these flaws to access other users� accounts, view sensitive files, or use unauthorized functions. |
A3 | Broken Authentication and Session Management | Account credentials and session tokens are not properly protected. Attackers that can compromise passwords, keys, session cookies, or other tokens can defeat authentication restrictions and assume other users� identities. |
A4 | Cross Site Scripting (XSS) Flaws | The web application can be used as a mechanism to transport an attack to an end user�s browser. A successful attack can disclose the end user�s session token, attack the local machine, or spoof content to fool the user. |
A5 | Buffer Overflows | Web application components in some languages that do not properly validate input can be crashed and, in some cases, used to take control of a process. These components can include CGI, libraries, drivers, and web application server components. |
A6 | Injection Flaws | Web applications pass parameters when they access external systems or the local operating system. If an attacker can embed malicious commands in these parameters, the external system may execute those commands on behalf of the web application. |
A7 | Improper Error Handling | Error conditions that occur during normal operation are not handled properly. If an attacker can cause errors to occur that the web application does not handle, they can gain detailed system information, deny service, cause security mechanisms to fail, or crash the server. |
A8 | Insecure Storage | Web applications frequently use cryptographic functions to protect information and credentials. These functions and the code to integrate them have proven difficult to code properly, frequently resulting in weak protection. |
A9 | Denial of Service | Attackers can consume web application resources to a point where other legitimate users can no longer access or use the application. Attackers can also lock users out of their accounts or even cause the entire application to fail. |
A10 | Insecure Configuration Management | Having a strong server configuration standard is critical to a secure web application. These servers have many configuration options that affect security and are not secure out of the box. |
Bruce Clay has mapped an interesting Search Engine Relationship Chart. It's interesting to see that Google is now the most important Search Engine for supplying informations. Bruce also points attention on Search Engine Optimization, Marketing strategies, Promotion metodology and tactics.
Thanks Bruce, it's really a good research...
As you know, there are several requirements to running a
.NET program (the first is obviously that the .NET Framework needs to be installed prior to installing your program). And if your target system don't have all this requirements?
Kevin Moore gives a solution with a creation of an
Enhanced .NET Bootstrap Setup.
An interesting article by Alex Calvo on MSDN Magazine shows the differences between the different Timers classes in the .NET Framework. The .NET Framework Class Library provides three different timer classes: System.Windows.Forms.Timer, System.Timers.Timer, and System.Threading.Timer. Each of these classes has been designed and optimized for use in different situations. This article examines the three timer classes and helps you gain an understanding of how and when each class should be used.
Check it!
Today a friend sent me an email signalling me Damn Small Linux, a new Linux distribution bootable from CD... it's based on Knoppix (my favourite CD Bootable Linux release) and obviously Debian... in particular this distribution in really small, only 50Mb, so very interesting to make bootable devices such as USB Pen.
Another interesting distribution to add to my last post here... I'll try it soon.