immauss / immauss/openvas

[BUG] Unable to get WMI working

Open
#331 31 comments 0 reactions 1 assignee Claimed by @immauss View on GitHub
Dominant language
Shell
Stars
481
Forks
117
PR merge metrics
No merged PRs in 30d

Description

Using the 25.01.01 container, and trying to perform a WMI scan against a known machine, I get

```
Description (Knowledge base entry) : Value/Content
--------------------------------------------------------------------------------------------------------------------------------
Access to the registry possible (SMB/registry_access) : TRUE
Access via WMI possible (WMI/access_successful) : FALSE
```

under the `Authenticated Scan / LSC Info Consolidation (Windows SMB Login)` report for a scan. Jumping into the container and running the `wmic` command, or the `impacket-wmic` command works as expected (I can get a response). However, there is nothing in the scanning logs, other than WMI access is denied or not available.

For comparison, I spun up the Greenbone community containers (that was a mission!!) and did a comparison scan. That scan was successful, and I received

```
Description (Knowledge base entry) : Value/Content
--------------------------------------------------------------------------------------------------------------------------------
Access to the registry possible (SMB/registry_access) : TRUE
Access via WMI possible (WMI/access_successful) : TRUE
```

So, how would I go about trying to troubleshoot this to provide some valid feedback??

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.