You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The program reports hosts running Windows 11 as Windows 10.
To Reproduce
Steps to reproduce the behavior i.e.:
Command: netexec smb [IP]
Resulted in:
``
└─# nxc smb 10.1.11.8
SMB 10.1.11.8 445 JM-SURFACE [*] Windows 10.0 Build 26100 x64 (name:JM-SURFACE) (domain:JM-SURFACE) (signing:True) (SMBv1:False)
Expected behavior
Should report Windows 11 (Build 26100 Googles as:
Windows 10.0 Build 26100 is associated with Windows 11, version 24H2, not Windows 10. Here are some key points about this build:"
@NeffIsBack does it fall back to Win10 or is it fully Impacket just reporting the wrong version? In other words can we just report "Unknown Windows" or do we have to rely fully on Impacket
@NeffIsBack does it fall back to Win10 or is it fully Impacket just reporting the wrong version? In other words can we just report "Unknown Windows" or do we have to rely fully on Impacket
Kinda. If no matching build number is found it does something like "Win {os.major_version}.{os.minor_version}". And since Win10 that was always "Win 10.0"
Describe the bug
The program reports hosts running Windows 11 as Windows 10.
To Reproduce
Steps to reproduce the behavior i.e.:
Command:
netexec smb [IP]
Resulted in:
``
└─# nxc smb 10.1.11.8
SMB 10.1.11.8 445 JM-SURFACE [*] Windows 10.0 Build 26100 x64 (name:JM-SURFACE) (domain:JM-SURFACE) (signing:True) (SMBv1:False)
Expected behavior
Should report Windows 11 (Build 26100 Googles as:
Windows 10.0 Build 26100 is associated with Windows 11, version 24H2, not Windows 10. Here are some key points about this build:"
NetExec info
The text was updated successfully, but these errors were encountered: