Differences between revisions 17 and 18
Revision 17 as of 2005-11-16 09:55:58
Size: 5848
Comment: add buffer code
Revision 18 as of 2005-11-16 14:35:38
Size: 5914
Editor: xdsl-195-14-205-204
Comment: buffer code is 2 byte, Reposnse Buffer Offset is known --metze
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
|                Buffer Code             | | Buffer Code | InfoClass |   Infolevel |
Line 18: Line 18:
| | | | | | Flags |
Line 34: Line 34:
["SMB2/BufferCode"] ["SMB2/BufferCode"] 0x29 = 0x28 | 0x01 (but why? where's the dynamic part?)
Line 36: Line 36:
== Buffer Code/Class ==
Class specifies what type of object we want information about.
== InfoClass ==
Infoclass specifies what type of object we want information about.
Line 43: Line 43:
== Buffer Code/InfoLevel ==
Infolevel together with Class specific a specific type of information to be returned.
== InfoLevel ==
Infolevel together with Infoclass specify a specific type of information to be returned.
Line 88: Line 88:
|               Buffer Code         | | Buffer Code | Response Buffer Offset |
Line 90: Line 90:
|        Response Buffer Size       | | Response Buffer Size (16 or 32 bit?) |
Line 92: Line 92:
| Data depending of Class/Infolevel in the request | Data depending of Infoclass/Infolevel in the request
Line 98: Line 98:
|               Buffer Code         | | Buffer Code | Response Buffer Offset |
Line 107: Line 107:
["SMB2/BufferCode"] ["SMB2/BufferCode"] 0x09 = 0x08 | 0x01

SMB2/GetInfo

Opcode 0x10

This command can be used to get information about files and other types of objects from the server.

SMB2/GetInfo Request

SMB2/GetInfo Request Packet Format

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          Buffer Code          |   InfoClass   |   Infolevel   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                   Max Response Buffer Size                    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|               |               |               |               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                             Flags                             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|               |               |               |               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|               |               |               |               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
+-+-+-+-+                      FID                      +-+-+-+-+
|                                                               |
+-+-+-+-+                                               +-+-+-+-+
|                                                               |
+-+-+-+-+                                               +-+-+-+-+
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Buffer Code

["SMB2/BufferCode"] 0x29 = 0x28 | 0x01 (but why? where's the dynamic part?)

InfoClass

Infoclass specifies what type of object we want information about.

0x01     SMB2_CLASS_FILE_INFO
0x02     SMB2_CLASS_FS_INFO
0x03     SMB2_CLASS_SEC_INFO

InfoLevel

Infolevel together with Infoclass specify a specific type of information to be returned.

Infolevels for SMB2_CLASS_FILE_INFO

  • 0x04 ["SMB2/SMB2_FILE_INFO_04"]
  • 0x05 ["SMB2/SMB2_FILE_INFO_05"]
  • 0x06 ["SMB2/SMB2_FILE_INFO_06"]
  • 0x07 ["SMB2/SMB2_FILE_INFO_07"]
  • 0x08 ["SMB2/SMB2_FILE_INFO_08"]
  • 0x0a ["SMB2/SMB2_FILE_INFO_0a"] (Set Filename used to rename files)
  • 0x0d ["SMB2/SMB2_FILE_INFO_0d"]
  • 0x0e ["SMB2/SMB2_FILE_INFO_0e"]
  • 0x0f ["SMB2/SMB2_FILE_INFO_0f"]
  • 0x10 ["SMB2/SMB2_FILE_INFO_10"]
  • 0x11 ["SMB2/SMB2_FILE_INFO_11"]
  • 0x12 ["SMB2/SMB2_FILE_INFO_12"]
  • 0x15 ["SMB2/SMB2_FILE_INFO_15"]
  • 0x16 ["SMB2/SMB2_FILE_INFO_16"]
  • 0x1c ["SMB2/SMB2_FILE_INFO_1c"]
  • 0x22 ["SMB2/SMB2_FILE_INFO_22"]
  • 0x23 ["SMB2/SMB2_FILE_INFO_23"]

Infolevels for SMB2_CLASS_FS_INFO

  • 0x01 ["SMB2/SMB2_FS_INFO_1"]
  • 0x03 ["SMB2/SMB2_FS_INFO_3"]
  • 0x04 ["SMB2/SMB2_FS_INFO_04"]
  • 0x05 ["SMB2/SMB2_FS_INFO_5"]
  • 0x06 ["SMB2/SMB2_FS_INFO_06"]
  • 0x07 ["SMB2/SMB2_FS_INFO_7"]
  • 0x08 ["SMB2/SMB2_FS_INFO_08"]

Infolevels for SMB2_CLASS_SEC_INFO

  • 0x00 ["SMB2/SMB2_SEC_INFO_00"]

Max Response Buffer Size

This field specifies the maximum amount of data that the server can send back in the response. If the response is truncated the server will set the NT Status Code STATUS_BUFFER_OVERFLOW

SMB2/GetInfo Response

SMB2/GetInfo Response Packet Format

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|           Buffer Code           |    Response Buffer Offset   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|               Response Buffer Size (16 or 32 bit?)            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|    Data depending of Infoclass/Infolevel in the request
+-+-+-+-+...

or 
if STATUS_BUFFER_TOO_SMALL
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|           Buffer Code           |    Response Buffer Offset   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                   Response Buffer Size == 4                   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                       Required Buffer Size                    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Buffer Code

["SMB2/BufferCode"] 0x09 = 0x08 | 0x01

Response Buffer Size

The number of bytes of returned data that follows.

NT Status Codes

  • 0xc0000023 STATUS_BUTTER_TOO_SMALL This indicates that the buffer was too small to hold the returned data. The response packet will only contain 4 bytes which represents the required size of the buffer.
  • 0x80000005 STATUS_BUFFER_OVERFLOW This indicates that the buffer was too small and that the response data is truncated. There is no indication of how big the buffer needs to be.

Discussion

Some of the 16 bytes between maxresponsebuffersize and the fid in the request holds data specific to the class/level used and will alter what kind of data is returned. Bytes 8-11 have been seen to definitely fall in this range. but it could be bytes 4-15 or even all of them. This blob should be documented on the corresponding class/level page.

Examples

Here is a [attachment:smb2-getinfo.cap capture] of a scanner trying every SMB2 getinfo level. The file being queried had the following settings:

scan-getinfo.dat:
        create_time:    Thu Aug 10 09:11:44 2006 EST
        access_time:    Fri May 12 09:11:44 2006 EST
        write_time:     Sat Feb 11 10:11:44 2006 EST
        change_time:    Sun Nov 13 10:08:13 2005 EST
        attrib:         0x20
        alloc_size:     8
        size:           7
        nlink:          1
        delete_pending: 0
        directory:      0
        ea_size:        41
        fname:          '\test\scan-getinfo.dat'

SMB2/GetInfo (last edited 2008-05-05 07:15:50 by GuyHarris)