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

Can't load scan.yml in Debial WSL2 Win 11 #1853

Open
HackThePlanetKC opened this issue Aug 8, 2024 · 0 comments
Open

Can't load scan.yml in Debial WSL2 Win 11 #1853

HackThePlanetKC opened this issue Aug 8, 2024 · 0 comments

Comments

@HackThePlanetKC
Copy link

Before submitting an issue, please make sure you fully read any potential error messages output and did some research on your own.

Subject of the issue

I have been following these instructions. I've tried to save my scan.yml file at ~/.wpscan/scan.yml and pwd/.wpscan/scan.yml inside Debian, and C:\Windows\System32\wpscan on my host. When I try to run a scan, it keeps returning "No WPScan API Token given, as a result vulnerability data has not been output.". It works just fine with --api-token argument.

Your environment

  • Version of WPScan: 3.8.25
  • Version of Ruby: 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu]
  • Operating System (OS): Host: Win 11 22631.3880, Debian: 12 (bookworm), Kernel version: 5.10.16

Steps to reproduce

Install WSL2 on Win11 machine, install Debian 12, install wpscan, configure scan.yml according to instructions, attempt to run.

Expected behavior

Vulnerability details should be shown in the results.

Actual behavior

The rest of the scan runs, but keeps returning "No WPScan API Token given" when trying to retrieve the vulnerability data.

What have you already tried

Tried changing where scan.yml is located, searched through forums. No documentation seems to exist for this issue in WSL.

Things you have tried (where relevant):

  • Update WPScan to the latest version [√ ]
  • Update Ruby to the latest version [√ ]
  • Ensure you can reach the target site using cURL [√ ]
  • Proxied WPScan through a HTTP proxy to view the raw traffic [N/A ]
  • Ensure you are using a supported Operating System (Linux and macOS) [√ ]
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

1 participant