-
Updated
Mar 21, 2022 - Go
vulnerabilities
Here are 475 public repositories matching this topic...
-
Updated
Mar 21, 2022 - Go
-
Updated
Mar 22, 2022 - Shell
-
Updated
Mar 13, 2022 - Ruby
-
Updated
Mar 22, 2022 - Python
-
Updated
Mar 1, 2022
-
Updated
Mar 21, 2022 - TypeScript
-
Updated
Oct 27, 2020 - Shell
What would you like to be added:
Please add some basic instructions for compiling the binaries to the install readme as an alternative to curl to bash.
Why is this needed:
Some folks are uncomfortable with the security implications of curl to bash
There are additional use cases where users may wish to modify the functionality of the project to better fit their needs
**Addit
-
Updated
Mar 1, 2022 - JavaScript
-
Updated
Mar 22, 2022
-
Updated
Nov 15, 2021 - Python
-
Updated
Mar 13, 2022 - Shell
-
Updated
Mar 21, 2022 - JavaScript
-
Updated
Mar 22, 2022 - Python
-
Updated
Mar 21, 2022 - Python
-
Updated
Mar 21, 2022 - PHP
-
Updated
Sep 28, 2021 - JavaScript
-
Updated
Dec 6, 2021 - C
Migration to bcrypt
Context
- This is part of
release-1.5#148 - MEDIUM priority task
Tasks
- Remove dependency
bcrypt-nodejsinpackage.json - Add dependency
bcryptinpackage.json - Migrate file app/data/user-dao.js to bcrypt
- Validate the instalation with the local test
- Add and submit the chang
Upgrade dependencies
-
Updated
Dec 25, 2021 - Go
Is this a request for help?: Yes
Is this a BUG REPORT or a FEATURE REQUEST? (choose one): FEATURE REQUEST
Can we add a option to allow the engine update vulnerabilities database through specific proxy ser
-
Updated
Mar 2, 2022
-
Updated
Mar 9, 2022 - Python
-
Updated
Jan 2, 2022
The current swagger definition is autogenerated. The automatically generated definitions rely on reflection and annotations to create the documentation. The reflection capabilities are poor at best and lead to missing API parameters. Annotations can help in some cases, but the only fix for Swagger is to create individual POJOs for every possible request. This will lead to unnecessary large number
-
Updated
Jun 15, 2021 - C
The products and vendors, which are listed in the affected Column of a CVE are often not vulnerable.
For example:
The CVE-2021-44738 has multiple configurations, but only one of each configuration is vulnerable.
From the first configuration only "b2236_firmware" is vulnerable, but not "b2236", if you check the JSON object.
<img width="603" alt="Screenshot 2022-03-06 013750" src="https://user-i
Improve this page
Add a description, image, and links to the vulnerabilities topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the vulnerabilities topic, visit your repo's landing page and select "manage topics."
I note that there is a check whether the cluster is deployed into Azure Cloud .. see below.
I don't have a problem with that per se except that in a corporate environment I don't want to request a proxy whitelist exception with my CISO for an endpoint that we have no use for (http://www.azurespeed.com). Moreover, whilst this test will eventually timeout and the checks resume, it delays the pro