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

Fingerprinting Windows 11 Hosts Reports as Windows 10 #543

Closed
johnmarosi opened this issue Jan 17, 2025 · 4 comments · Fixed by fortra/impacket#1874
Closed

Fingerprinting Windows 11 Hosts Reports as Windows 10 #543

johnmarosi opened this issue Jan 17, 2025 · 4 comments · Fixed by fortra/impacket#1874
Labels
dependencies Pull requests that update a dependency file

Comments

@johnmarosi
Copy link

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

@NeffIsBack
Copy link
Contributor

Yep thanks for the report.
Impacket just hasn't updated the build number list yet. Gonna PR the new build numbers when i have time

@NeffIsBack NeffIsBack added the dependencies Pull requests that update a dependency file label Jan 17, 2025
@Marshall-Hallenbeck
Copy link
Collaborator

@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
Copy link
Contributor

@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"

@NeffIsBack
Copy link
Contributor

Should be fixed with fortra/impacket#1874

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants