This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "OWASP SonarQube Project"

From OWASP
Jump to: navigation, search
Line 4: Line 4:
  
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
−
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
+
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |  
 +
 
 +
'''NOTE:''' If you are interested in contributing to open source static vulnerability analysis for Java, OWASP recommends you contribute to the [http://find-sec-bugs.github.io/ Find Security Bugs Project] run by Philippe Arteau. FindSecBugs is a FindBugs plugin. Philippe also runs the [https://github.com/SonarQubeCommunity/sonar-findbugs SonarQube FindBugs Plugin Project], which bundles both FindBugs and FindSecBugs into a plugin that can be used with SonarQube and in fact comes bundled with SonarQube by default. So, by contributing to the Find Security Bugs project, you are helping both the Find Bugs and SonarQube user communities at the same time.
 +
 
 +
 
 
THIS PROJECT HAS BEEN RELEASED TO OWASP AND WELCOMES NEW LEADERS
 
THIS PROJECT HAS BEEN RELEASED TO OWASP AND WELCOMES NEW LEADERS
  
 
[https://docs.google.com/a/owasp.org/document/d/14gOrrfp5-JmWUVL6XaOMMbcWhxY-P3_mvncvZZRIVgg/edit?usp=sharing| Project Abandonment Release Form Completed on 5/17/16 by Ann Campbell, Freddy Maller, Sebastian Gloria]
 
[https://docs.google.com/a/owasp.org/document/d/14gOrrfp5-JmWUVL6XaOMMbcWhxY-P3_mvncvZZRIVgg/edit?usp=sharing| Project Abandonment Release Form Completed on 5/17/16 by Ann Campbell, Freddy Maller, Sebastian Gloria]
  
−
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#).
+
----
 +
 
 +
Historical Info:
 +
 
 +
The first goal of the OWASP SonarQube Project is to a create a referential of check specifications targeting 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 :
 
Any contributor is highly welcome to participate to this community effort and participating is pretty easy :

Revision as of 20:48, 21 June 2016

OWASP Inactive Banner.jpg

NOTE: If you are interested in contributing to open source static vulnerability analysis for Java, OWASP recommends you contribute to the Find Security Bugs Project run by Philippe Arteau. FindSecBugs is a FindBugs plugin. Philippe also runs the SonarQube FindBugs Plugin Project, which bundles both FindBugs and FindSecBugs into a plugin that can be used with SonarQube and in fact comes bundled with SonarQube by default. So, by contributing to the Find Security Bugs project, you are helping both the Find Bugs and SonarQube user communities at the same time.


THIS PROJECT HAS BEEN RELEASED TO OWASP AND WELCOMES NEW LEADERS

Project Abandonment Release Form Completed on 5/17/16 by Ann Campbell, Freddy Maller, Sebastian Gloria

Historical Info:

The first goal of the OWASP SonarQube Project is to a create a referential of check specifications targeting 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 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.


Project Leader

Sebastien Gioria

Freddy Mallet

G. Ann Campbell

Email List

Sign Up!

Archives


Repository

Here are the repositories for the open source plugins related to this project. Most of them provide security-related rules:


Classifications

New projects.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files CODE.jpg
  • 26 Mar 2016: Release of the SonarQube C# plugin version 5.0 adds four new bug and security-related rules:
    • S1944 Inappropriate casts should not be made
    • S3466 Optional parameters should be passed to "base" calls
    • S3449 Right operands of shift operators should be integers
    • S2184 Result of integer division should not be assigned to floating point variable


  • 25 Mar 2016: Release of the SonarQube Java plugin version 3.12 adds three new bug and security-related rules:
    • S3066 "enum" fields should not be publicly mutable
    • S3034 Raw byte values should not be used in bitwise operations in combination with shifts
    • S3546 Resources as defined by user should be closed

This last is actually a rule template, which will allow users to raise issues appropriately on their custom Resources.


  • 6 Feb 2016: Release of the SonarQube Java plugin version 3.10 adds seven new bug and security-related rules:
    • S2142 "InterruptedException" should not be ignored
    • S3438 "SingleConnectionFactory" instances should be set to "reconnectOnException"
    • S3281 Default EJB interceptors should be declared in "ejb-jar.xml"
    • S2639 Inappropriate regular expressions should not be used
    • S3369 Security constraints should be defired
    • S3374 Struts validation forms should have unique names
    • S3355 Web applications should use validation filters






  • 1 July 2015: Release of the SonarQube JavaScript plugin version 2.7 adds 6 new rules, including 2 bug-related rules, 1 CWE-related rule, and 2 rules directly related to security
    • RSPEC-930 The number of arguments passed to a function shall match the number of parameters
    • RSPEC-2819 Cross-document messaging domains should be carefully restricted
    • RSPEC-2817 Web SQL databases shoudl not be used
  • 9 March 2015: With its latest release, version 3.0 on 4 March 2015, the SonarQube Java plugin now covers 50 different CWE items. See the full list
  • 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
  • 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
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....

Sponsors :

AppSec Blog ; AppSecFR Coach - Sébastien Gioria Consulting

SonarSource ; Founder and maintainer of SonarQube

PROJECT INFO
What does this OWASP project offer you? 		RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP SonarQube Project
Purpose: The OWASP SonarQube project aims to provide open source SAST using the existing open source solutions. SonarQube is one of the world’s most popular continuous code quality tools and it's actively used by many developers and companies.

This project aims to enable more security functionalities to SonarQube and use it as an SAST. This project will use open source sonar plugins, rules, as well as other open source plugins especially FindSecBugs and its security rules. FindSecBugs enables the taint analysis.

License: LGPL v3
who is working on this project?
Project Leader(s):
  • Vinod Anandan @
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: [[email protected] Mailing List Archives]
Project Roadmap: Not Yet Created
Key Contacts
  • Contact Vinod Anandan @ to contribute to this project
  • Contact Vinod Anandan @ to review or sponsor this project
current release
Not Yet Published
last reviewed release
Not Yet Reviewed


other releases

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_SonarQube_Project&oldid=218145"