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

Problem: technique T1018 is throwing errors after the last update on the main branch #2583

Closed
Vjeroen opened this issue Nov 2, 2023 · 3 comments
Assignees

Comments

@Vjeroen
Copy link

Vjeroen commented Nov 2, 2023

What did you do?

Invoke-AtomicTest -AtomicTechnique T1018 -TestNumbers 17

What did you expect to happen?

Expected a list of domain computers

Atomic needs to list domain computers

What happened instead?

PS Error that states it executed technique 5 instead of 17:

Get-AtomicTechnique : [C:\AtomicRedTeam\atomics\T1018\T1018.yaml][Atomic test name:
Remote System Discovery - arp nix] 'atomic_tests[5].supported_platforms': 'freebsd'
must be one of the following: windows, macos, linux, office-365, azure-ad, google-workspace, saas, iaas, containers, iaas:aws, iaas:azure, iaas:gcp. At C:\AtomicRedTeam\invoke-atomicredteam\Public\Invoke-AtomicTest.ps1:343 char:71 + ... aml) { $AtomicTechniqueHash = Get-AtomicTechnique -Path $pathToYaml } + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-At

Your Environment

Windows 10

  • Which specific operating system are you running (e.g. Windows 7 SP1 32-bit)? Windows 10 64bit
  • Did you run the test from an elevated or root prompt? yes
  • If relevant, which atomic test is this specific to? T1018 17
  • If relevant, which execution harness are you attempting to use?
@cyberbuff cyberbuff self-assigned this Nov 3, 2023
@cyberbuff
Copy link
Collaborator

Thanks for reporting the issue. Working on it now. Should be fixed within Nov 3.

@cyberbuff
Copy link
Collaborator

cyberbuff commented Nov 3, 2023

Should be fixed once #2585 and #166 are merged.

@cyberbuff
Copy link
Collaborator

This should be fixed now

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