Test Kennung:	1.3.6.1.4.1.25623.1.0.803514
Kategorie:	Nmap NSE
Titel:	Nmap NSE 6.01: smb-security-mode
Zusammenfassung:	Returns information about the SMB security level determined by SMB.;;Here is how to interpret the output:;; - User-level authentication: Each user has a separate username/password that is used to log into the;system. This is the default setup of pretty much everything these days.;; - Share-level authentication: The anonymous account should be used to log in, then the password is given (in;plaintext) when a share is accessed. All users who have access to the share use this password. This;was the original way of doing things, but isn't commonly seen, now. If a server uses share-level;security, it is vulnerable to sniffing.;; - Challenge/response passwords supported: If enabled, the server can accept any type of password (plaintext, LM and NTLM, and LMv2 and NTLMv2). If it isn't;set, the server can only accept plaintext passwords. Most servers are configured to use;challenge/response these days. If a server is configured to accept plaintext passwords, it is;vulnerable to sniffing. LM and NTLM are fairly secure, although there are some brute-force attacks;against them. Additionally, LM and NTLM can fall victim to man-in-the-middle attacks or relay;attacks (see MS08-068 or the referenced writeup of it.).;; - Message signing: If required, all messages between the client and server must be signed by a shared key,;derived from the password and the server challenge. If supported and not required, message signing;is negotiated between clients and servers and used if both support and request it. By default,;Windows clients don't sign messages, so if message signing isn't required by the server, messages;probably won't be signed. Additionally, if performing a man-in-the-middle attack, an attacker can;negotiate no message signing. If message signing isn't required, the server is vulnerable to man-in-;the-middle attacks or SMB-relay attacks.;;This script will allow you to use the 'smb*' script arguments (to set the username and;password, etc.), but it probably won't ever require them.;;SYNTAX:;;smbbasic: Forces the authentication to use basic security, as opposed to 'extended security'.;Against most modern systems, extended security should work, but there may be cases;where you want to force basic. There's a chance that you'll get better results for;enumerating users if you turn on basic authentication.;;smbport: Override the default port choice. If 'smbport' is open, it's used. It's assumed;to be the same protocol as port 445, not port 139. Since it probably isn't possible to change;Windows' ports normally, this is mostly useful if you're bouncing through a relay or something.;;smbsign: Controls whether or not server signatures are checked in SMB packets. By default, on Windows,;server signatures aren't enabled or required. By default, this library will always sign;packets if it knows how, and will check signatures if the server says to. Possible values are:;; - 'force': Always check server signatures, even if server says it doesn't support them (will;probably fail, but is technically more secure).;; - 'negotiate': [default] Use signatures if server supports them.;; - 'ignore': Never check server signatures. Not recommended.;; - 'disable': Don't send signatures, at all, and don't check the server's. not recommended.;More information on signatures can be found in 'smbauth.lua'.;;randomseed: Set to a value to change the filenames/service names that are randomly generated.
Beschreibung:	Summary: Returns information about the SMB security level determined by SMB. Here is how to interpret the output: - User-level authentication: Each user has a separate username/password that is used to log into the system. This is the default setup of pretty much everything these days. - Share-level authentication: The anonymous account should be used to log in, then the password is given (in plaintext) when a share is accessed. All users who have access to the share use this password. This was the original way of doing things, but isn't commonly seen, now. If a server uses share-level security, it is vulnerable to sniffing. - Challenge/response passwords supported: If enabled, the server can accept any type of password (plaintext, LM and NTLM, and LMv2 and NTLMv2). If it isn't set, the server can only accept plaintext passwords. Most servers are configured to use challenge/response these days. If a server is configured to accept plaintext passwords, it is vulnerable to sniffing. LM and NTLM are fairly secure, although there are some brute-force attacks against them. Additionally, LM and NTLM can fall victim to man-in-the-middle attacks or relay attacks (see MS08-068 or the referenced writeup of it.). - Message signing: If required, all messages between the client and server must be signed by a shared key, derived from the password and the server challenge. If supported and not required, message signing is negotiated between clients and servers and used if both support and request it. By default, Windows clients don't sign messages, so if message signing isn't required by the server, messages probably won't be signed. Additionally, if performing a man-in-the-middle attack, an attacker can negotiate no message signing. If message signing isn't required, the server is vulnerable to man-in- the-middle attacks or SMB-relay attacks. This script will allow you to use the 'smb*' script arguments (to set the username and password, etc.), but it probably won't ever require them. SYNTAX: smbbasic: Forces the authentication to use basic security, as opposed to 'extended security'. Against most modern systems, extended security should work, but there may be cases where you want to force basic. There's a chance that you'll get better results for enumerating users if you turn on basic authentication. smbport: Override the default port choice. If 'smbport' is open, it's used. It's assumed to be the same protocol as port 445, not port 139. Since it probably isn't possible to change Windows' ports normally, this is mostly useful if you're bouncing through a relay or something. smbsign: Controls whether or not server signatures are checked in SMB packets. By default, on Windows, server signatures aren't enabled or required. By default, this library will always sign packets if it knows how, and will check signatures if the server says to. Possible values are: - 'force': Always check server signatures, even if server says it doesn't support them (will probably fail, but is technically more secure). - 'negotiate': [default] Use signatures if server supports them. - 'ignore': Never check server signatures. Not recommended. - 'disable': Don't send signatures, at all, and don't check the server's. not recommended. More information on signatures can be found in 'smbauth.lua'. randomseed: Set to a value to change the filenames/service names that are randomly generated. CVSS Score: 9.3 CVSS Vector: AV:N/AC:M/Au:N/C:C/I:C/A:C
Querverweis:	Common Vulnerability Exposure (CVE) ID: CVE-2008-4037 BugTraq ID: 7385 http://www.securityfocus.com/bid/7385 Cert/CC Advisory: TA08-316A http://www.us-cert.gov/cas/techalerts/TA08-316A.html https://www.exploit-db.com/exploits/7125 HPdes Security Advisory: HPSBST02386 http://marc.info/?l=bugtraq&m=122703006921213&w=2 HPdes Security Advisory: SSRT080164 http://www.networkworld.com/news/2008/111208-microsoft-seven-year-security-patch.html http://www.securityfocus.com/data/vulnerabilities/exploits/backrush.patch http://www.securityfocus.com/data/vulnerabilities/exploits/backrush.patch.README http://www.veracode.com/blog/2008/11/microsoft-fixes-8-year-old-design-flaw-in-smb/ http://www.xfocus.net/articles/200305/smbrelay.html Microsoft Security Bulletin: MS08-068 https://docs.microsoft.com/en-us/security-updates/securitybulletins/2008/ms08-068 http://osvdb.org/49736 https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6012 http://securitytracker.com/id?1021163 http://secunia.com/advisories/32633 http://www.vupen.com/english/advisories/2008/3110
Copyright	Copyright (C) 2013 NSE-Script: The Nmap Security Scanner; NASL-Wrapper: Greenbone Networks GmbH

Dies ist nur einer von 99761 Anfälligkeitstests in unserem Testpaket. Finden Sie mehr über unsere vollständigen Sicherheitsüberprüfungen heraus. Um einen gratis Test für diese Anfälligkeit auf Ihrem System durchlaufen zu lassen, registrieren Sie sich bitte unten.