-
Updated
Jun 21, 2021 - Shell
vulnerability-detection
Here are 212 public repositories matching this topic...
-
Updated
Jun 25, 2021 - Go
-
Updated
Jun 25, 2021 - Go
-
Updated
Jun 25, 2021 - Java
-
Updated
Mar 16, 2021 - Python
-
Updated
Jan 28, 2020 - Ruby
-
Updated
Jun 25, 2021 - C
-
Updated
Jun 13, 2021 - Lua
-
Updated
Jun 16, 2021 - Python
-
Updated
Feb 12, 2021 - Python
-
Updated
Apr 16, 2021 - Python
-
Updated
Jun 24, 2021 - C
-
Updated
Nov 26, 2020 - BitBake
-
Updated
May 14, 2021 - Python
-
Updated
Jun 17, 2021 - Perl
-
Updated
Jun 17, 2021 - Python
-
Updated
May 28, 2021 - Python
-
Updated
Jun 21, 2021 - Shell
Current Behavior:
When viewing vulns in the Audit Vulnerabilities tab. the Analysis column appears to contain code (enum?) names, e.g. NOT_SET, FALSE_POSITIVE. This problem also occurs in Policy Violations tab.
Steps to Reproduce:
Open the Audit Vulnerabilities tab.
Expected Behavior:
The Analysis column contains language specific analysis values, e.g. Not Set, False Positive
-
Updated
May 18, 2021
-
Updated
Jan 10, 2020 - JavaScript
-
Updated
Jun 2, 2021 - Python
-
Updated
Apr 26, 2021
-
Updated
May 31, 2021 - Ruby
Feedback
I think that you are doing a very necessary system and your idea is cool, but at the moment it has a lot of bugs. From what I noticed, the assets do not understand the ascii characters and the system crashes. In addition, I did not find a description of the API, I would like to integrate your system into TheHive, or rather make it possible to view information about an asset in TheHive. I believe t
-
Updated
Apr 20, 2020 - Python
-
Updated
Jun 24, 2021 - Python
-
Updated
Jun 4, 2021 - Python
-
Updated
Sep 28, 2018 - Python
Improve this page
Add a description, image, and links to the vulnerability-detection topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the vulnerability-detection topic, visit your repo's landing page and select "manage topics."
Currently, Trivy traverses all paths and looks for all Gemfile.lock in a container image. However, the image sometimes has only Gemfile.lock and doesn't install gems listed in the Gemfile.lock. I think a gem should have *.gemspec file if it is installed. e.g.
rake.gemspec
has the information aboutrake
.To avoid false positives from Gemfile.lock, we are probably able to take advantage of `*