Skip to content

Filter the vulnerabilities based upon CVEs of dependency check report in Sonar qube #1051

Closed
@Mukul1586

Description

@Mukul1586

Describe the bug
Hi team, we are using latest version of dependency-check-sonar-plugin and we have integrated the Dependency check report with SonarQube. We can see the vulnerabilities in app under security tag or under OWASP section in SonarQube. However, all these vulnerabilities are coming under same the rule which is "using components with known vulnerabilities".
Our requirement is to filter the vulnerabilities based upon CVEs across multiple projects in Sonar Qube. We already reached out to SonarQube team and they have suggested that this requirement is based upon the plugin capability. Kindly suggest

To Reproduce
It would be helpful when you support us with example projects.
Steps to reproduce the behavior:

  1. Install '...'
  2. Run '
  3. Login to '....'
  4. See error

Current behavior
We can see the vulnerabilities in app under security tag or under OWASP section in SonarQube. However, all these vulnerabilities are coming under same the rule which is "using components with known vulnerabilities".

Expected behavior
Expectation is that we would be able to filter the vulnerabilities based upon CVEs across multiple projects in Sonar Qube. We already reached out to SonarQube team and they have suggested that this requirement is based upon the plugin capability.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

  • dependency-check:-
  • sonarqube: 10.3
  • dependency-check-sonar-plugin:- 5.0.*

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions