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

docs(issue): added docs for wrong detection issues #1961

Merged
merged 8 commits into from
Apr 12, 2022

Conversation

afdesk
Copy link
Contributor

@afdesk afdesk commented Apr 6, 2022

Description

Added information about wrong detection issues to the docs.

Checklist

  • I've read the guidelines for contributing to this repository.
  • I've followed the conventions in the PR title.
  • I've added tests that prove my fix is effective or that my feature works.
  • I've updated the documentation with the relevant information (if needed).
  • I've added usage information (if the PR introduces new options)
  • I've included a "before" and "after" example to the description (if the PR is a user interface change).

@afdesk afdesk marked this pull request as ready for review April 12, 2022 05:55
@afdesk afdesk changed the title docs(issue): added a template for wrong security advisory docs(issue): added docs for wrong detection issues Apr 12, 2022
@afdesk afdesk requested a review from knqyf263 April 12, 2022 05:57
Comment on lines 8 to 21
## Wrong detection
Trivy depends on Github Advisory Database and Gitlab Advisory Database.
Sometime these databases contain mistakes.

if Trivy can't detect any CVEs or shows false positive result, at first do the next steps:
- run Trivy with `-f json` that shows data sources. Please make sure that data source is correct.
- visit [Github Advisory Database](https://github.com/advisories) and search CVE-ID.
- visit [Gitlab Advisory Database](https://advisories.gitlab.com/) and search CVE-ID .

If the data source is correct and Trivy shows wrong results, please raise an issue on Trivy

If you find a problem, it'll be nice to fix it:
* How to contribute to a GitHub security advisory: https://github.blog/2022-02-22-github-advisory-database-now-open-to-community-contributions/
* Create an issue to Gitlab Advisory Database: https://gitlab.com/gitlab-org/security-products/gemnasium-db/-/issues/new
Copy link
Collaborator

@knqyf263 knqyf263 Apr 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mkdocs may show different from GitHub markdown. Please make sure that the doc is not broken by make mkdocs-serve. It seems to be broken now.

image

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll fix it this time.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll fix it this time.

oh, thanks. will be careful

Comment on lines 13 to 16
## Check Advisory Databases
- [ ] run Trivy with `-f json` that shows data sources. Please make sure that data source is correct.
- [ ] visit [Github Advisory Database](https://github.com/advisories) and search CVE-ID.
- [ ] visit [Gitlab Advisory Database](https://advisories.gitlab.com/) and search CVE-ID.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Check Advisory Databases
- [ ] run Trivy with `-f json` that shows data sources. Please make sure that data source is correct.
- [ ] visit [Github Advisory Database](https://github.com/advisories) and search CVE-ID.
- [ ] visit [Gitlab Advisory Database](https://advisories.gitlab.com/) and search CVE-ID.
## Checklist
- [ ] Read [the documentation regarding wrong detection](https://aquasecurity.github.io/trivy/latest/community/contribute/issue/#wrong-detection)
- [ ] Confirm that a security advisory in data sources is correct
- run Trivy with `-f json` that shows data sources. Please make sure that the security advisory is correct.

Comment on lines 6 to 12
<!--

Please, read the documentation before creating an issue:
https://aquasecurity.github.io/trivy/latest/community/contribute/issue/

-->

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can move it to check list.

@@ -4,3 +4,18 @@ Thank you for taking interest in contributing to Trivy!
- Please spend a small amount of time giving due diligence to the issue tracker. Your issue might be a duplicate. If it is, please add your comment to the existing issue.
- Remember that users might search for your issue in the future, so please give it a meaningful title to help others.
- The issue should clearly explain the reason for opening, the proposal if you have any, and any relevant technical information.

## Wrong detection
Trivy depends on Github Advisory Database and Gitlab Advisory Database.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Trivy depends on Github Advisory Database and Gitlab Advisory Database.
Trivy depends on [multiple data sources](https://aquasecurity.github.io/trivy/latest/docs/vulnerability/detection/data-source/).

Trivy depends on Github Advisory Database and Gitlab Advisory Database.
Sometime these databases contain mistakes.

if Trivy can't detect any CVEs or shows false positive result, at first do the next steps:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if Trivy can't detect any CVEs or shows false positive result, at first do the next steps:
If Trivy can't detect any CVE-IDs or shows false positive result, at first please follow the next steps:

@knqyf263 knqyf263 merged commit 72d94b2 into main Apr 12, 2022
@knqyf263 knqyf263 deleted the docs/advisory-issue-template branch April 12, 2022 06:57
liamg pushed a commit that referenced this pull request Jun 7, 2022
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

Successfully merging this pull request may close these issues.

3 participants