Skip to content

ERROR: Unable to map scan scope variable to a value. #6

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

Open
Bowen73 opened this issue Dec 15, 2021 · 2 comments
Open

ERROR: Unable to map scan scope variable to a value. #6

Bowen73 opened this issue Dec 15, 2021 · 2 comments

Comments

@Bowen73
Copy link

Bowen73 commented Dec 15, 2021

im running this via ps but when I run it I get the below error without asking what option I want to run:

PS D:\log4j> .\scanner-8b.ps1
Log4j/Log4Shell CVE-2021-44228 Scanning/Mitigation Tool (seagull/Datto)
=======================================================================
! ERROR: Unable to map scan scope variable to a value. (This should never happen!)
  The acceptable values for env:usrScanScope are:
    1: Scan files on Home Drive
    2: Scan files on fixed and removable drives
    3: Scan files on all detected drives, even network drives
PS D:\log4j>
@nixuno
Copy link

nixuno commented Dec 15, 2021

Before running the script you need to set three variables:

$env:usrScanscope = # 1, 2, or 3 - 1 = Scan home drive, 2 = scan fixed and removable, 3 = scan all local and network drives
$env:usrUpdateDefs = # 'true' or 'false' - Update YARA definitions, true or false
$env:usrMitigate = # 'Y', 'N', or 'X' - Y = Set LOG4J_FORMAT_MSG_NO_LOOKUPS to true, N = Set LOG4J_FORMAT_MSG_NO_LOOKUPS to false, X = Don't set LOG4J_FORMAT_MSG_NO_LOOKUPS

@Datto-StanLee
Copy link

Datto-StanLee commented Dec 16, 2021

Well-put. You can also find this in the readme under "usage".

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

3 participants