OWASP SonarQube Project

=Main=



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

The first goal of the OWASP SonarQube Project is to a create a referential of check specifications targetting OWASP vulnerabilities and that can be detected by SAST tools (Static Application Security Testing). From there, the second goal is to provide a reference implementations of most of those checks in the Open Source SonarQube language analysers (Java, JavaScript, PHP and C#).

Any contributor is highly welcome to participate to this community effort and participating is pretty easy :
 * Each idea of a new potential valuable check should be sent to this project mailing list.
 * Then some discussions might start to challenge the idea
 * At the end of discussions, a specification of the check is created in the following JIRA project by one of the leader of this project : http://jira.sonarsource.com/browse/RSPEC.
 * To suggest a rule, send as much as possible from the following list:
 * description - What should be done/not done, and why
 * noncompliant code example in the language of your choice
 * remediation action - This can be as simple as "Don't do X."

The "News" is updated as soon as :
 * A check specification is created
 * A SonarQube analysers containing some stuff relating to this OWASP SonarQube project is released.

About SonarQube
SonarQube is an Open Source platform for managing code quality. This platform can be extended with Open Source or commercial plugins, see for instance the Java, JavaScript, PHP and C# plugins.

Licensing
OWASP SonarQube Project is free to use. It is licensed under the [ttp://www.apache.org/licenses/LICENSE-2.0 Apache 2.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.


 * valign="top" style="padding-left:25px;width:200px;" |

Project Leader
[mailto:sebastien.gioria@owasp.org Sebastien Gioria]

[mailto:freddy.mallet@sonarsource.com Freddy Mallet]

[mailto:ann.campbell@sonarsource.com G. Ann Campbell]

Email List
Sign Up!

Archives

Classifications

 * }

= News =
 * 5 February 2015: Release of SonarQube Java 2.9.1 plugin containing 19 new rules including 1 related to OWASP Top 10:
 * RSPEC-2257 Only standard cryptographic algorithms should be used


 * 5 January 2015: Release of SonarQube Java 2.8 plugin containing 25 new rules including several related to OWASP Top 10:
 * RSPEC-2277 Cryptographic RSA algorithms should always incorporate OAEP (Optimal Asymmetric Encryption Padding)
 * RSPEC-2078 Values passed to LDAP queries should be sanitized
 * RSPEC-2076 Values passed to OS commands should be sanitized
 * RSPEC-2278 DES (Data Encryption Standard) and DESede (3DES) should not be used


 * 12 December 20014 : Release of SonarQube Java 2.7 plugin containing 26 new rules and 7 relating to OWASP TOP 10
 * RSPEC-2068 Credentials should not be hard-coded
 * RSPEC-2245 Pseudorandom number generators (PRNGs) should not be used in secure context
 * RSPEC-2255 Cookies should not be used to store sensitive information
 * RSPEC-2089 HTTP referers should not be relied on
 * RSPEC-2070 SHA-1 and MD5 hash algorithms should not be used
 * RSPEC-2254 "HttpServletRequest.getRequestedSessionId" should not be used
 * RSPEC-2258 "javax.crypto.NullCipher" should not be used for anything other than testing


 * 10 December 2014 : 2 new rules specified
 * RSPEC-2278 DES (Data Encryption Standard) and DESede (3DES) should not be used
 * RSPEC-2277 Cryptographic RSA algorithms should always incorporate OAEP (Optimal Asymmetric Encryption Padding)


 * 3 December 2014 : 4 new rules specified
 * RSPEC-2258	"javax.crypto.NullCipher" should not be used for anything other than testing
 * RSPEC-2257	Only standard cryptographic algorithms should be used
 * RSPEC-2255	Cookies should not be used to store sensitive information
 * RSPEC-2254	"HttpServletRequest.getRequestedSessionId" should not be used


 * 6 November 2014 : Project presentation at Application Security Forum West Switzerland


 * 1 November 2014 : new "owasp-top10" tag in the "Rules" space to quickly search for OWASP Top 10 relating rules (mainly Findbugs rules)
 * RSPEC-2077	Values passed to SQL commands should be sanitized


 * 2 October 2014 : 2 new rules specified
 * RSPEC-2092	Cookies should be "secure"
 * RSPEC-2091	Values passed to XPath expressions should be sanitized
 * RSPEC-2089	HTTP referers should not be relied on
 * RSPEC-2087	Weak encryption should not be used
 * RSPEC-2086	Values passed to XQuery commands should be sanitized
 * RSPEC-2085	Values passed to HTTP redirects should be neutralized
 * RSPEC-2084	Messages output from a servlet "catch" block should be invariable
 * RSPEC-2083	Values used in path traversal should be neutralized


 * 1 October 2014 : Matching most of the SonarQube rules to the MITRE CWE referential to ease the tagging of "owasp-top10" relating rules


 * 11 September 2014 : Project as been presented at OWASP France Meeting. See Air Mozilla recording

=FAQs=


 * How do I use the owasp-top10 tag?
 * Perform a rule search for tag=owasp-top10. If you have the proper permissions, you can use the bulk change options to activate the results in your profiles.


 * How to help ?
 * Give us your expertise on some langage, or ability to test on some real project our rules, or more...


 * Will you plan other langage ?
 * Yes, contact us if you want to know more. And perhaps give us some feedback one some real projects....

= Acknowledgements =

Sponsors :
Advens ; French Experts on application security

SonarSource ; Founder and maintainer of SonarQube

=Project About=