Skip to content


N-Stalker's Team Blog

OWASP Top10 2010 Released!

A couple of weeks ago, OWASP – Open Web Application Security Project published the new version of its most widely known project: OWASP TOP 10. This is the third edition of such project that deals with the 10 greatest found in web applications.

Compared with 2007′s previous edition, the list of has not changed that much, with code injection failures (ex: SQL Injection, command injection, etc.) and Cross-Site Scripting occupying the top of the list again. Please see the comparative table below:

OWASP Top 10 – 2007

OWASP Top 10 – 2010 (New)

A2 – Injection Flaws

A1 – Injection

A1 – Cross Site Scripting (XSS)

A2 – Cross-Site Scripting (XSS)

A7 – Broken Authentication and Session Management

A3 – Broken Authentication and Session Management

A4 – Insecure Direct Object Reference

A4 – Insecure Direct Object Reference

A5 – Cross Site Request Forgery (CSRF)

A5 – Cross-Site Request Forgery (CSRF)

<was T10 2004 A10 – Insecure Configuration Management>

A6 – Security Misconfiguration (New)

A8 – Insecure Cryptographic Storage

A7 – Insecure Cryptographic Storage

A10 – Failure to Restrict URL Access

A8 – Failure to Restrict URL Access

A9 – Insecure Communications

A9 – Insufficient Transport Layer Protection

<not present on Top 10 2007>

A10 – Unvalidated Redirects and Forwards (New)

A3 – Malicious File Execution

<Removed from Top 10 2010>

A6 – Information Leakage and Improper Error Handling

< Removed from Top 10 2010>

OWASP is a non-profit organization created in 2003 with the mission to make application security visible so that individuals and organizations could be able to make well informed decisions about real application security risks. Bearing in mind that have become more evident in the application layer (and no longer in the network layer as occurred 5 years ago) is of the utmost importance that enterprises and corporations of all sizes using systems internally or externally developed get to know more about the potential risks present in Web applications.

The document in English, in its whole integrity, is made available HERE and soon its version in Portuguese will be also released, translated by both OWASP Brazil’s and OWASP Portugal’s communities.

’s solution is fully able to validate your environment against listed on TOP 10 2010. Contact us!

No tags for this post.

Related posts

Posted in N-Stalker's Team Blog.

Publicado o OWASP Top 10 2010

Na segunda-feira passada, a OWASP – Open Web Application Security Project, publicou a nova versão de seu projeto mais conhecido: OWASP TOP 10. Esta é a terceira edição do projeto que trata sobre as 10 maiores vulnerabilidades em aplicações Web.

Comparada com a edição anterior de 2007, a lista das vulnerabilidades não mudou muito, sendo que as falhas de injeção de código (ex: SQL Injection, command injection, etc) e Cross-Site Scripting encabeçaram a lista novamente. Veja a tabela comparativa:

OWASP  Top 10 – 2007 (Anterior)

OWASP Top 10 – 2010 (Novo)

A2 – Injection Flaws

A1 – Injection

A1 – Cross Site Scripting (XSS)

A2 – Cross-Site Scripting (XSS)

A7 – Broken Authentication and Session Management

A3 – Broken Authentication and Session Management

A4 – Insecure Direct Object Reference

A4 – Insecure Direct Object Reference

A5 – Cross Site Request Forgery (CSRF)

A5 –  Cross-Site Request Forgery (CSRF)

<was T10 2004 A10 – Insecure Configuration Management>

A6 – Security Misconfiguration (Nova)

A8 – Insecure Cryptographic Storage

A7 – Insecure Cryptographic Storage

A10 – Failure to Restrict URL Access

A8 – Failure to Restrict URL Access

A9 – Insecure Communications

A9 – Insufficient Transport Layer Protection

<não presente no Top 10 2007>

A10 – Unvalidated Redirects and Forwards (Nova)

A3 – Malicious File Execution

<Removida do Top 10 2010>

A6 – Information Leakage and Improper Error Handling

< Removida do Top 10 2010>

A OWASP é uma organização sem fins lucrativos que surgiu em 2003 com a missão de tornar a segurança de aplicação visível, de forma que pessoas e organizações possam tomar decisões bem informadas sobre os verdadeiros riscos de segurança de aplicações. Por conta das estarem mais evidentes na camada de aplicação, e não mais na camada de rede como há 5 anos atrás, é de extrema importância que empresas e corporações de todos os tamanhos e que utilizem sistemas desenvolvidos internamente ou externamente conheçam mais os potenciais riscos presentes em aplicações Web.

O documento em inglês na integra pode ser obtido AQUI e em breve será divulgada a  versão em Português, traduzida pelas comunidades OWASP Brasil e OWASP Portugal.

A solução da N-Stalker está preparada para validar seu ambiente contra as vulnerabilidades listadas no TOP 10 2010.

No tags for this post.

Related posts

Posted in N-Stalker's Team Blog.

Fim da era da serie 1.3 do Apache Server / End of Life for Apache 1.3 series

Portugues(pt_BR)

Certamente todo administrador linux ou de segurança já trabalhou com a serie 1.3 do Apache. Certamente ela deixara saudades para a velha guarda mais a evolução é necessária . Foi anunciado hoje (02/02/2010) a última versão da serie apache 1.3 . No release  1.3.42 informaram o fim da era da versão 1.3 e que o mesmo terá somente alguns críticos .

Parte do anúncio (Inglês)

“The Apache Software Foundation and the Apache HTTP Server Project are pleased to announce the release of version 1.3.42 of the Apache HTTP Server (“Apache”). This release is intended as the final release of version 1.3 of the Apache HTTP Server, which has reached end of life status.”

Anúncio completo:

http://mail-archives.apache.org/mod_mbox/httpd-announce/201002.mbox/%3C20100203000334.GA19021@infiltrator.stdlib.net%3E

Visando a proteção de nossos clientes no futuro sugerimos que façam para versões correntes assim que possível visto que problemas de segurança podem surgir. Abaixo as melhores versões para uso:

Apache HTTP Server 2.2.14 is the best available version
Apache 2.0.63 Released

Mais informações: http://httpd.apache.org/download.cgi

Team

English(en)

Probably every linux administrator or security analyst have been worked with Apache 1.3 series . The old school guys will miss but the evolution is necessary . Today was announced the lastest release for apache 1.3 series. In this release 1.3.42 they announced that apache 1.3 will only have critical .

Part of the announce:

“The Apache Software Foundation and the Apache HTTP Server Project are pleased to announce the release of version 1.3.42 of the Apache HTTP Server (“Apache”). This release is intended as the final release of version 1.3 of the Apache HTTP Server, which has reached end of life status.”

Full announce:

http://mail-archives.apache.org/mod_mbox/httpd-announce/201002.mbox/%3C20100203000334.GA19021@infiltrator.stdlib.net%3E

Looking forward to protect and advise our costumer we really suggest you to update to current versions as listed bellow:

Apache HTTP Server 2.2.14 is the best available version
Apache 2.0.63 Released

More information: http://httpd.apache.org/download.cgi

Team

No tags for this post.

Related posts

Posted in N-Stalker's Team Blog.

N-Stalker is 2009′s winning web application security software, says security-database!

SECURITY-DATABASE, one of world’s most accredited entities dedicated to identify and assess web security (as well as the best available on the market to combat them) has nominated as 2009′s winner in web application .

This is the result of 10 years fully dedicated to the creation, design and development of state-of-the-art, outstanding software solutions now adoptedby governmental, public and legal entities as well as and worldwide.

Another jewel in our crown and a challenge to keep up the good work!


escolhido como melhor em 2009!

O site SECURITY-DATABASE, uma das mais conceituadas entidades dedicadas à identificação e avaliação de à segurança na Web (como também na indicação das melhores ferramentas disponíveis no mercado para combatê-las) declarou o software vencedor em 2009 na categoria de ferramentas de em da Web.

Este nada mais é que o resultado de 10 anos plenamente dedicados à criação, projeto e desenvolvimento de soluções de software de segurança na Web no estado-da-arte, hoje adotadas por governos, empresas públicas e privadas, e na Web, por todo o mundo.

Mais uma jóia em nossa coroa e mais um desafio para nos mantermos no topo em 2010!

Tags: , , , , , , , , , , , , , , ,

Related posts

Posted in Announcements, N-Stalker's Team Blog. Tagged with , , , , , , , , , , , , , , , .

Cross Site Scripting (XSS) Twitter / WafW00f release 0.24

Primeiramente comentarei de um XSS encontrado no twitter pelo time da junto com o time da iBliss (http://www.ibliss.com.br) . Fazendo alguns testes rotineiros encontramos uma situação aparentemente não muito fácil de explorar globalmente mas com possibilidades de roubo de sessão dentre outros fatores.

O twitter tem um campo de pesquisas http://www.twitter.com/timeline/search?q= .

Se digitassemos algo como <script language=javascript>alert(‘XSS’)</script> no search nada aconteceria. O problema seria quando você  salvasse o search e realizando o reload na página o código era carregado .

A falha foi reportada para o security do twitter

Discovered                        29/11/2009
Vendor Disclosure       02/12/2009
Patched                              09/12/2009
Disclosure                        09/12/2009

A correção foi extremamente rápida e vale parabenizar a equipe de desenvolvedores/equipe de segurança do twitter.

Além do report do XSS testamos o release 0.24 do WafW00f escrito pelo Sandro Gauci e pelo nosso amigo Wendel aka Dumdum. Essa ferramenta visa detectar a presença de web application firewalls e com isso colaborar com uso de possíveis técnicas de evasion para bypassar e ter maior sucesso no pentest ou analise de vulnerabilidade web .

A ferramenta suporta a detecção dos seguintes WAF’s

spooker@notsecure:/LABS/waffit$ python wafw00f.py –list

WAFW00F – Web Application Firewall Detection Tool

By Sandro Gauci && Wendel G. Henrique

Can test for these WAFs:

Profense
NetContinuum
Barracuda
HyperGuard
BinarySec
Teros
F5 Trafficshield
F5 ASM
Airlock
Citrix NetScaler
ModSecurity
DenyALL
dotDefender
webApp.secure
BIG-IP
URLScan
WebKnight
SecureIIS
BeeWare
Imperva

spooker@notsecure:/LABS/waffit$

A ferramenta basicamente envia algumas requisições consideradas maliciosas pela maioria dos web application firewalls e baseado nas respostas enumera o que está sendo utilizado . Fiz um teste em um hosting que conheço que utiliza Imperva e o resultado foi perfeito.

Algumas das requisições maliciosas enviadas pelo mesmo :

send: ‘GET /../../../../etc/passwd HTTP/1.1\r\nHost: www.domain.com\r\nAccept-Encoding: identity\r\nAccept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\nAccept: */*\r\nUser-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b1) Gecko/20081007 Firefox/3.0\r\n\r\n’

send: ‘GET / HTTP/1.1\r\nHost: www.domain.com\r\nAccept-Encoding: identity\r\nTransfer-Encoding: zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz<RECORTADO>\r\nAccept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\nAccept: */*\r\nUser-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b1) Gecko/20081007 Firefox/3.0\r\n\r\n’

send: ‘GET /cmd.exe HTTP/1.1\r\nHost: www.domain.com\r\nAccept-Encoding: identity\r\nAccept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\nAccept: */*\r\nUser-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b1) Gecko/20081007 Firefox/3.0\r\n\r\n’

spooker@notsecure:/LABS/waffit$ python wafw00f.py http://www.domain.com

WAFW00F – Web Application Firewall Detection Tool

By Sandro Gauci && Wendel G. Henrique

Checking http://www.domain.com
The site http://www.domain.com is behind a Imperva
Number of requests: 8
spooker@notsecure:/LABS/waffit$

A ferramenta é bem interessante para ajudar no uso ou não de técnicas de evasion e não sei se existem números ainda quanto a eficácia da mesma em todas os WAFs listados mas certamente a ferramenta continua em crescimento e vamos aguarda o release 0.25 .

Links:

http://waffit.googlecode.com/
http://pentestit.com/2009/12/13/update-wafw00f-revision-24/

Aproveitando a equipe da gostaria de desejar Feliz Natal e Ótimo Ano Novo a todos que nos acompanham.

Team

No tags for this post.

Related posts

Posted in N-Stalker's Team Blog.

Brazilian Blackout – Our comments on “The true about blackout post”

Much has been spoken last week about reasons for the great blackout occurred on November 10th, 2009. The Brazilian government has reported atmospheric problems as its main cause but was quite a coincidence that a CBS 60-minute report had been broadcasted, informing that the Brazilian power grid system was vulnerable to hacker attacks.

To make reasons for blackout even more confused, Maycon Vitali, security researcher and professor at UVV in Vila Velha, Espirito Santo State, Brazil, has issued a post without blog  (pt_BR http://blog.hacknroll.com/2009/11/12/a-verdade-sobre-o-apagao/) demonstrating flaws in web security in the ONS site (Brazil’s National Operating System)  through which he received thousands of accesses to post which has been heavily commented in the web community, posted in big media vehicles like infoexame, G1, e Band among others, with many referenced made to such post on personal blogs and twitter.

We believe that many people have wrongly analyzed the contents of such post as well as a great (and unnecessary) hullabaloo has been made about this matter.

Below we will comment on such post and some erroneous interpretations.

Firstly, has been comment about robots.txt in the ONS site:


What’s robots.txt?

As the name says, is a file in txt format that works as a filter for crawlers, enabling webmasters to control access permissions to specific points in the sites. The robots.txt controls which information item from a site should (or should not) be indexed by the browsing sites. File syntax is very simple and should be placed by the webmaster responsible for the site in the roots of hosting.

In the case of the mentioned robots.txt, blocks any user-agent that is performing crawler action and in two directories:

User-agent: *
Disallow: /agentes/agentes.aspx
Disallow: /download/agentes/

By accessing the site in the directories that should not be indexed in the browsers we noticed in the links (for some applications like citrix) a web system where the post in the blog was originated.

Based on the post reports he says that he tried to access an application in the presented list and in the login he tried to use simple inverted commas, thus causing the result below:

“[IfxException: ERROR [HY000] [Informix .NET provider]General error.] IBM.Data.Informix.IfxConnection.HandleError(IntPtr hHandle, SQL_HANDLE hType, RETCODE retcode) +27 IBM.Data.Informix.IfxCommand.ExecuteReaderObject(CommandBehavior behavior, String method) +739 IBM.Data.Informix.IfxCommand.ExecuteReader(CommandBehavior behavior) +104 IBM.Data.Informix.IfxCommand.ExecuteReader() +48 OnsClasses.OnsData.OnsCommand.ExecuteReader() IntUnica.Menu.btnOk_Click(Object sender, ImageClickEventArgs e) System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e) +109 System.Web.UI.WebControls.ImageButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +69 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +18 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain() +1292″

As I mentioned in mailling lists and in comments with friends that based on post and error message showed WE CANNOT STATE that there is a SQL injection in the application as was only an exception (stack) that had been printed on the screen and would thus be an “A6- Information Leakage and Improper Error Handling” failure. Logically, if we analyze statistics about this type of error, the majority will lead us to find the SQL Injection itself as being an Informix error. Logically, if we check statistics on this type of error, the majority will lead us to find the SQL injection itself as being an Informix error. To find the truth would be necessary to accomplish tests, what would be illegal as we do not have authorization for such..

What would be an A6-  Information Leakage and Improper Error Handling failure?

Several applications may, unintentionally, leak information about their configurations, internal functioning or violate privacy through several problems. Applications can leak their internal functioning via response time to execute specific process or different responses for diverse entries, like displaying same error message but with different error codes. Web Applications will frequently leak information about their internal functioning through detailed error messages or debug. Frequently, these information items can be the path to launch attacks or even more powerful .

Conclusions:

-Access to agents cannot be regarded as a failure since robots.txt are globally used so that information cannot be indexed in the searchs as google, yahoo  but, when dealing with applications, would be a best practice to place an access password in the directory /agents/.

- A stack error or inadequate error handling does not mean that the site has some SQL Injection vulnerability in the application, however, one may notice that data input sanitization has not been accomplished.

- We do not know what can be found inside the applications, what gives no reason for such hullabaloo in case a SQL Injection is confirmed to have some relation with the big blackout.

-Internally there they must have perimeter defense , stronger authentication engines, but, as informed, such information is based only on assumptions.

-The Brazilian Government should invest more in web security in its environments and logically make use of Web Vulnerability Analysis as well as use Web Application Firewall (WAF) and also develop internally a Secure Development LifeCycle (SDLC).

Team

No tags for this post.

Related posts

Posted in N-Stalker's Team Blog.