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.

Sign up for GitHub

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

Jump to bottom

Scan Aborted: metadata.json: checksums do not match #1463

Closed
23vbq opened this issue Mar 8, 2020 · 3 comments
Closed

Scan Aborted: metadata.json: checksums do not match #1463

23vbq opened this issue Mar 8, 2020 · 3 comments

Comments

@23vbq
Copy link

23vbq commented Mar 8, 2020

When I using wpscan it gives Scan aborted: metadata.json: checksums do not match

  • Version of WPScan: 3.7.9
  • Version of Ruby: 2.5.7p206
  • Operating System (OS): Kali Linux 2020.1 (GNOME)

Here is output:
`
vblacqe@okali:~$ wpscan --update

     __          _______   _____
     \ \        / /  __ \ / ____|
      \ \  /\  / /| |__) | (___   ___  __ _ _ __ ®
       \ \/  \/ / |  ___/ \___ \ / __|/ _` | '_ \
        \  /\  /  | |     ____) | (__| (_| | | | |
         \/  \/   |_|    |_____/ \___|\__,_|_| |_|

     WordPress Security Scanner by the WPScan Team
                     Version 3.7.9
                           
   @_WPScan_, @ethicalhack3r, @erwan_lr, @firefart

[i] Updating the Database ...

Scan Aborted: metadata.json: checksums do not match
Trace: /var/lib/gems/2.5.0/gems/wpscan-3.7.9/lib/wpscan/db/updater.rb:151:in block in update' /var/lib/gems/2.5.0/gems/wpscan-3.7.9/lib/wpscan/db/updater.rb:141:in each'
/var/lib/gems/2.5.0/gems/wpscan-3.7.9/lib/wpscan/db/updater.rb:141:in update' /var/lib/gems/2.5.0/gems/wpscan-3.7.9/app/controllers/core.rb:47:in update_db'
/var/lib/gems/2.5.0/gems/wpscan-3.7.9/app/controllers/core.rb:57:in before_scan' /var/lib/gems/2.5.0/gems/cms_scanner-0.8.4/lib/cms_scanner/controllers.rb:46:in each'
/var/lib/gems/2.5.0/gems/cms_scanner-0.8.4/lib/cms_scanner/controllers.rb:46:in block in run' /usr/lib/ruby/2.5.0/timeout.rb:76:in timeout'
/var/lib/gems/2.5.0/gems/cms_scanner-0.8.4/lib/cms_scanner/controllers.rb:45:in run' /var/lib/gems/2.5.0/gems/cms_scanner-0.8.4/lib/cms_scanner/scan.rb:24:in run'
/var/lib/gems/2.5.0/gems/wpscan-3.7.9/bin/wpscan:17:in block in <top (required)>' /var/lib/gems/2.5.0/gems/cms_scanner-0.8.4/lib/cms_scanner/scan.rb:15:in initialize'
/var/lib/gems/2.5.0/gems/wpscan-3.7.9/bin/wpscan:6:in new' /var/lib/gems/2.5.0/gems/wpscan-3.7.9/bin/wpscan:6:in <top (required)>'
/usr/bin/wpscan:23:in load' /usr/bin/wpscan:23:in

'
`
I have been tried to:

  • Update WPScan to the latest version
  • Reinstall wpscan
  • Update Ruby to the latest version
  • Reinstall ruby
  • Reinstall gem
@firefart
Copy link
Contributor

firefart commented Mar 8, 2020

Have you tried updating again?

@mielczarus
Copy link

I have similar problems with wpscan updateing. The output is the same like above.

@firefart
Copy link
Contributor

firefart commented Mar 8, 2020

Please try the update again. I just tried it and it works without problems:

[i] Updating the Database ...
[i] File(s) Updated:
 |  metadata.json
 |  wp_fingerprints.json
 |  timthumbs-v3.txt
 |  config_backups.txt
 |  db_exports.txt
 |  dynamic_finders.yml
 |  LICENSE
 |  sponsor.txt
[i] Update completed.

@firefart firefart closed this as completed Mar 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@firefart @mielczarus @23vbq