-
|Wazuh v4.7.0|Vulnerability Detector|test VM|Manual install|RockyLinux 9.3|
If I am not mistaken Wazuh supports the file based V1.1 API of the NIST nvd data-feeds (https://nvd.nist.gov/vuln/data-fe…
-
**What happened**:
Grype is reporting a (very old) vulnerability in the `webrick` ruby gem despite running a version with the fix:
```
> docker run --rm -it -v /var/run/docker.sock:/var/run/docke…
-
* terrascan version:
* Operating System:
### Description
The latest tag published at https://hub.docker.com/r/tenable/terrascan/tags is 1.18.11. It looks like the latest release published was 1…
parse updated
2 months ago
-
See https://nvd.nist.gov/vuln/detail/CVE-2017-18640
This could possibly be caused by the addition of `PassthroughConstructor`
-
I execute dependency-check in cmd
dependency-check
--nvdApiKey "########-####-####-####-############
--scan "D:\\###\scanlib"
--out "D:\\###\report"
--format "JSON"
The following situat…
-
|Wazuh version|Component|Install type|Platform|
|---|---|---|---|
| 4.8.0 | Vulnerability Engine | Manager/Agent | windows |
With the upgrade to the new Wazuh 4.8.0 engine, the manager reports …
-
The enhancement may already be reported! Please search for the enhancement before creating one.
### Current Behavior:
Currently feeds are downloaded as whole file
### Proposed Behavior:
Use NV…
-
Current Status:
If I create a component or import a list of components I will have the issue that from time to time my vendorname or productname does not fit the NVD writing, or i cant provide a cpe …
-
I'm using Dependency Track "for real", monitoring several products and hundreds of components.
Sometimes DTrack does not report a vulnerability I know is applicable. The reason is that the "affecte…
-
In #3903 I discussed some ideas about improving how we use our NVD mirrors and making sure users understand when the mirrors are available, and I'm separating those out into more doable issues now.
…