-
Updated
Sep 2, 2021 - Python
vulnerability-management
Here are 88 public repositories matching this topic...
-
Updated
Sep 3, 2021 - Go
-
Updated
Aug 23, 2021 - Python
-
Updated
Sep 2, 2021 - JavaScript
-
Updated
Sep 2, 2021 - C
-
Updated
Jul 31, 2021 - Python
-
Updated
Jul 1, 2020 - Java
-
Updated
Jan 10, 2020 - JavaScript
-
Updated
Aug 24, 2021 - HCL
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
Jul 18, 2018 - Python
-
Updated
Aug 17, 2021 - Go
-
Updated
Aug 28, 2021
-
Updated
Aug 12, 2021 - Python
There are the following to messages:
https://github.com/greenbone/gvmd/blob/v20.8.0/src/gvmd.c#L2648
https://github.com/greenbone/gvmd/blob/v20.8.0/src/manage_sql.c (Line 934)
I don't know the details on both message and for which cases these are showing up but it could help for issues like #1270 to include some info on gvmd --migrate
and other special cases (e.g. if a downgrade is trie
-
Updated
Jan 19, 2020 - C++
-
Updated
Sep 3, 2021 - XSLT
-
Updated
Aug 21, 2021 - TypeScript
-
Updated
Oct 1, 2018 - Swift
-
Updated
Sep 2, 2021 - JavaScript
-
Updated
Sep 1, 2021 - TypeScript
-
Updated
Jun 14, 2021 - Python
-
Updated
Jan 13, 2021 - HTML
-
Updated
Aug 30, 2021 - Python
-
Updated
Aug 30, 2021 - Vue
-
Updated
Aug 17, 2020 - Lua
-
Updated
Aug 30, 2021 - Python
g_memdup has been deprecated since glib version 2.68. Use g_memdup2 instead.
3 instances of g_memdup in gvm-libs:
/opt/gvm/src/gvm-libs/base/networking.c on lines 368 and 374
/opt/gvm/src/gvm-libs/util/kb.c on line 634
Improve this page
Add a description, image, and links to the vulnerability-management topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the vulnerability-management topic, visit your repo's landing page and select "manage topics."
Slack us first!
Hello. I write about problem here:
https://owasp.slack.com/archives/C2P5BA8MN/p1624892081234100
Be informative
As additional into slack I find the same behaviour with Risk Accepted findings. Into Metrics I see 0 Risk Accepted findings, but I have 1 Risk Accepted finding
Bug description
No error. Metrics into product, or metrics dushboard has incorrect info