Skip to content
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

Exploitdb integration #121

Open
lvets opened this issue May 12, 2016 · 2 comments
Open

Exploitdb integration #121

lvets opened this issue May 12, 2016 · 2 comments

Comments

@lvets
Copy link

lvets commented May 12, 2016

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!

@PidgeyL
Copy link
Owner

PidgeyL commented May 17, 2016

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.

PidgeyL pushed a commit that referenced this issue May 17, 2016
Small bugfixes and plug-in features
@PidgeyL
Copy link
Owner

PidgeyL commented Jun 14, 2016

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants