-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Include Support for EUVD (European Union Vulnerability Database) #7608
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
Comments
If they were to provide machine-consumable resource that would be a very good idea. However at first glance they appear to offer a website-based service for human consumption without a machine-consumable resource/service. |
There is an API at: And I found some preliminary / unofficial documentation of the API here: Greetings Michael |
Those links exactly proof my point: There is only a propriatety API, which someone has been working on an attempt to reverse-engineer it from the website. If the API would be targeting consumption by anything but the website there would be either an official API documentation or an official API client on the EUVD website. |
I reached them through the feedback form to try to get more information if they have anything planned that would allow Dependency-Check to contact the API. I will share information if I get some. |
Hello, @nhumblot Thank you for contacting them. After the news about MITRE (https://krebsonsecurity.com/2025/04/funding-expires-for-key-cyber-vulnerability-database/), which has been a very important warning of the weakness of this ecosystem, I think it is important to locate alternative sources to have an updated Database of CVEs. And if DependencyCheck can have access to them, I think they will be more than welcome. |
This looks official now. |
Are there any plans for including support for the European Union Vulnerability Database (EUVD) as an additional vulnerability source in DependencyCheck? Even though CISA has extended the CVE contract, many (EU-based) users and enterprises would probably appreciate that.
The text was updated successfully, but these errors were encountered: