You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How are cve-search and exploit-db integrated? The reason I ask is because I expected a link to the exploit-db somehow when opening for instance CVE-2016-0801 in cve-search. This CVE has a page with an exploit on exploit-db.com: https://www.exploit-db.com/exploits/39801/
Thanks in advance!
The text was updated successfully, but these errors were encountered:
The reason this is not implemented, is because exploitDB changed their format recently. We didn't want to integrate it yet, while the format was broken. This has been reported to @toolswatch, the developer of vFeed, who fixed this issue. We can now have a look to add this link.
Adding this information would conflict with the way CVE-search automates the displaying of information. If we start making rules like this, to check for specific database keys, to then add another entry, we'll end up creating a monster. Maybe you should report this to the vFeed project?
How are cve-search and exploit-db integrated? The reason I ask is because I expected a link to the exploit-db somehow when opening for instance CVE-2016-0801 in cve-search. This CVE has a page with an exploit on exploit-db.com: https://www.exploit-db.com/exploits/39801/
Thanks in advance!
The text was updated successfully, but these errors were encountered: