Since the SRD is once again downplaying SMB client side bug i think it’s important to share this kind of tricks.
It’s also important to mention that Browser and NBNS abusing is well known since a long time, as theses protocols wasn’t developed with security in mind, this blog post is a simple real case example.
There’s two way to automate SMB client side bug;
- NBNS Spoofing (require some “kind” of user interaction in some way, anyways in a corporate network it works pretty well)
- Browser Protocol Abusing (the funny one)
In this case I will cover a form of Browser Protocol Abusing.
The basic goal of this attack is to hijack the Local Master Browser (LMB), and there’s various way to do so;
- Register via NBNS on the Workgroup or domain, and launch an election (zero filled election packet), the winning criteria is first the browser version, and then the box capabilities, which is controlled by us.
- Create a NBNS name/ip conflict with the LMB and after 3 shot send a “Name Overwrite Demand” packet
- Reset the LMB
Why targeting the LMB ?
Simple, the Backup browser will sync via SMB (NetServerEnum2) on the LMB every 15 mn.
We don’t care that much about the Backup Browser, what we want it’s the DMB, and guess what, he’s also syncing on the LMB as soon you send him a Browser MasterAnnouncement :]
In this case, i will wait for a HostAnnouncement, a LocalMasterAnnouncement or an ElectionResquest, then I will send two LMB ResetBrowserState;
– one Reset_state clear_all
– one Reset_state stop_master
Which will directly kill the LMB (at least on Windows implementation).
Then you can launch an election that you’re sure to win (as mentionned before),
make a Local Master Browser Announcement, and finally a MasterAnnouncement, then the DMB will connect direclty to your fake server and get pwned (or not).
Here’s a quickly made proof of concept which work pretty well , it also have a NBNS spoofer just in case an admin try to access a share:]
I included a proof of concept for a previously discovered bug patched in february (MS10-006), you can find the full advisory here: http://seclists.org/fulldisclosure/2010/Feb/168
Note: Make sure your SMB server/exploit listen on 139 and 445, and can handle NBSS session request, if not, you wont get any candy.
Since Blogger is not python friendly: http://pastebin.com/YBtzs9yr
A bug like MS10-006 can be easily wormable if exploited with this kind of approach.
Go to Source of this post
Author Of this post: