Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop the rule S3649 #1386

Closed
dbolkensteyn opened this issue May 8, 2018 · 6 comments
Closed

Drop the rule S3649 #1386

dbolkensteyn opened this issue May 8, 2018 · 6 comments
Assignees
Milestone

Comments

@dbolkensteyn
Copy link
Contributor

The following rule as currently implemented in SonarCSharp is generating too many false-positives:

  • RSPEC-3649 SQL queries should not be vulnerable to injection attacks

It is about to be re-implemented using the taint analysis technique in SonarSecurity, for which we expect better results. However, because the same rule key will be re-used, it is a pre-requisite to first remove it from SonarCSharp prior to be able to ship SonarSecurity in SonarQube 7.2.

@agigleux
Copy link
Member

It also means SonarC# 7.2 (the version match is a coincidence) must be released before SonarQube 7.2 so that SonarC# can be embedded into it without S3649.

@dbolkensteyn
Copy link
Contributor Author

Of course @agigleux , and most importantly we need the UCFG producing code to be released as well

@Evangelink
Copy link
Contributor

We will need to fix the FIX ME inside CSharpSonarWayProfileTest.java after this ticket is done.

@dbolkensteyn
Copy link
Contributor Author

@Evangelink can you add a link to that FIXME? I don't see any in CSharpSonarWayProfileTest.java nor CSharpSonarWayProfile.java

@Evangelink
Copy link
Contributor

@dbolkensteyn It's linked to @benzonico PR that's about to be merged.

@benzonico
Copy link
Contributor

benzonico commented May 23, 2018

@Evangelink I would expect the FIXME to be removed by dropping the rule. The drop of the rule should lead this test to fail and as such to be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants