View Issue Details

IDProjectCategoryView StatusLast Update
0004103Kali LinuxGeneral Bugpublic2020-06-13 17:13
Reporterdjoun Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionsuspended 
Product Version2017.1 
Summary0004103: smbclient and enum4linux didnt show the smb version
Description

when i download vm version of 2017.1,
smbclient version is 4.5.8
after i do update with apt get update all, the version change to 4.6.5
after change then smbclient didnt show the smb version of the target

Steps To Reproduce

download vm version 2017.1
do update with apt get update all
smbclient -L [target]

Additional Information

i also attach the image with circle to show the diff between smbclient 4.5.8 and 4.6.5

Attached Files
458 to 465.pdf (200,065 bytes)

Relationships

related to 0004495 closed Some functions of enum4linux are incompatible with recent versions of smbclient 
related to 0004687 closed Smbclient does not print smb version 

Activities

g0tmi1k

g0tmi1k

2017-07-17 16:40

administrator   ~0006908

Does it relate to this? https://www.samba.org/samba/security/CVE-2016-2111.html

The following constraints are applied to SMB1 connections:
"client lanman auth = yes" is now consistently required for authenticated connections using the SMB1 LANMAN2 dialect.
"client ntlmv2 auth = yes" and "client use spnego = yes" (both the default values), require extended security (SPNEGO) support from the server. That means NTLMv2 is only used within NTLMSSP.

What happens if you where todo:
smbclient -L 11.22.33.44 -U Administrator%Password --option=clientntlmv2auth=no

djoun

djoun

2017-07-17 23:38

reporter   ~0006909

i just try it and result still same,
didnt show the samba version of the target

b4ndit

b4ndit

2017-11-20 03:49

reporter   ~0007612

I'm using a completely up-to-date version of Kali (which currently uses smbclient 4.7.1) and I can confirm this is still an issue.

I encountered the issue when I was trying to solve the Kioptrix Level 1 VM since it relies on smbclient being able to fingerprint the service version.

The only workable solution I've found to get around this issue is to use Metasploit's smb_version script. If anybody knows of a better work-around, please let me know.

g0tmi1k

g0tmi1k

2018-02-21 10:06

administrator   ~0008778

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x/2017.1), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2017-07-17 16:14 djoun New Issue
2017-07-17 16:14 djoun File Added: 458 to 465.pdf
2017-07-17 16:40 g0tmi1k Note Added: 0006908
2017-07-17 23:38 djoun Note Added: 0006909
2017-11-20 03:49 b4ndit Note Added: 0007612
2018-01-25 10:30 g0tmi1k Relationship added related to 0004495
2018-02-21 10:06 g0tmi1k Status new => closed
2018-02-21 10:06 g0tmi1k Resolution open => suspended
2018-02-21 10:06 g0tmi1k Note Added: 0008778
2018-04-09 14:15 g0tmi1k Relationship added related to 0004687