Incorrect date in files_exploits.csv

offensive-security / exploitdb

The legacy Exploit Database repository - New repo located at https://gitlab.com/exploit-database/exploitdb

https://gitlab.com/exploit-database/exploitdb

GNU General Public License v2.0

7.74k stars 1.88k forks source link

Incorrect date in files_exploits.csv #206

Closed hsvhora closed 2 years ago

hsvhora commented 3 years ago

Hi,

Since starting of this month (September-2021), date mapping against exploit-id is not proper, even all dates are showing same value 1970-01-01

File : file_exploits.csv

CaledoniaProject commented 3 years ago

+1, please fix it ASAP

id,file,description,date,author,type,platform,port
9,exploits/windows/dos/9.c,"Apache 2.x - Memory Leak",1970-01-01,"Matthew Murphy",dos,windows,

DaVieS007 commented 3 years ago

yes, unix_timestamp: 0 in all records

4lph4b commented 3 years ago

bump

thewhiteh4t commented 3 years ago

still facing this issue, please fix soon

matreurai commented 2 years ago

Up Please ! Still facing this problem and it makes it very unnecessary hard to filter exploits

4lph4b commented 2 years ago

137 days and counting since Offensive Security was notified about this issue.

19,021 days and counting since any exploits have been found according to this repo.

DaVieS007 commented 2 years ago

I think every should fix that by their own

anthony-dandrea commented 2 years ago

If the data is intentionally incorrect, why include it at all?

4lph4b commented 2 years ago

If the data is intentionally incorrect, why include it at all?

Why publish this git repo then? searchsploit is dead.

DaVieS007 commented 2 years ago

do we have alternatives?

thewhiteh4t commented 2 years ago

I even tweeted and tagged them but absolutely no response, looks like they dont care

nicolas-carolo commented 2 years ago

do we have alternatives?

You can try HoundSploit that offers many features including date fix. You can select the Database to use in Settings.

CaledoniaProject commented 2 years ago

I've opened a ticket in offensive security and they replied today:

We are unable to provide an exact date to solve the issue. However, our team will take into the case within this month.

wirespecter commented 2 years ago

@offensive-security It's been almost a year and this hasn't been fixed yet

thewhiteh4t commented 2 years ago

still waiting for a fix...

wirespecter commented 2 years ago

@offensive-security @g0tmi1k Any update on this? Lots of people want this to be fixed.

skontar commented 2 years ago

Anyone knows any workaround?

eaubin commented 2 years ago

You could approximate the dates from the git history

slriv3ra commented 2 years ago

Any update on this issue?

offensive-security commented 2 years ago

Sorry for the delay. Thank you for the bug report.

The 2022 update should fix it: https://www.offensive-security.com/offsec/exploit-db-2022-update/

$ head -n 1 files_exploits.csv; grep '^9,' files_exploits.csv
id,file,description,date_published,author,type,platform,port,date_added,date_updated,verified,codes,tags,aliases,screenshot_url,application_url,source_url
9,exploits/windows/dos/9.c,"Apache 2.x - Memory Leak",2003-04-09,"Matthew Murphy",dos,windows,,2003-04-08,2017-10-04,1,OSVDB-9712;CVE-2003-0132,,,,http://www.exploit-db.comhttpd-2.0.44.tar.gz,
$

You should be able to get updates now from: https://gitlab.com/exploit-database/exploitdb If you are still having issues, open up a ticket here: https://gitlab.com/exploit-database/exploitdb/-/issues.

g0tmi1k commented 2 years ago

@wirespecter, Sorry for the delay in getting back to you - I haven't really used gitHUB since migrating over to gitLAB