Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Sharepoint privilege escalation - admin.dll+author.dll |
|---|---|
| Date: | 27 Apr 2006 16:08:00 -0000 |
Hi list,
I'm testing a sharepoint portal running on IIS 6.0.The exact version (banner
based) is:
MicrosoftSharePointTeamServices: 6.0.2
I've identified the folllowing dlls, which are viewable (and perhaps
modifiable, if the list helps) by non-admin accounts:
/_vti_bin/_vti_adm/admin.dll
/_vti_bin/_vti_aut/author.dll
/_vti_bin/shtml.dll
When viewed, the first two return the following screen:
method=
status=
* status=262147
* osstatus=0
* msg=No "CONTENT_TYPE" in CGI environment.
* osmsg=
whilst the shtml.dll returns a 'sharepoint error' message.
I did some serious googling and attempted various POST attacks that reportedly
(http://www.packetstormsecurity.org/9910-exploits/webfolders.txt)
used to work (priv. escalation) back in the day. but without success. I've also
seen a BlackHat presentation from 2003 covering the same methods of attack
(carefully crafted POSTing). These methods refer to Frontpage extensions, but I
assume that the same principles are in use in sharepoint.
I wonder if anyone out there has any interesting ideas or ways to achieve
privilege escalation in such a scenario, or do anything othewise 'bad'. I'm not
too optimistic, as this being a standard microsoft application must have been
extensively tested before release and old bugs must have been fixed. Or not?
On another note, does one need to keep this files accessible/viewable at all?
Many thanks
Stelios
------------------------------------------------------------------------------
This List Sponsored by: Cenzic
Concerned about Web Application Security?
Why not go with the #1 solution - Cenzic, the only one to win the Analyst's
Choice Award from eWeek. As attacks through web applications continue to rise,
you need to proactively protect your applications from hackers. Cenzic has the
most comprehensive solutions to meet your application security penetration
testing and vulnerability management needs. You have an option to go with a
managed service (Cenzic ClickToSecure) or an enterprise software
(Cenzic Hailstorm). Download FREE whitepaper on how a managed service can
help you: http://www.cenzic.com/news_events/wpappsec.php
And, now for a limited time we can do a FREE audit for you to confirm your
results from other product. Contact us at request@cenzic.com for details.
------------------------------------------------------------------------------
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Licensed Penetration Tester LPT, Damien Dinh |
|---|---|
| Next by Date: | Core Impact vs. Canvas vs. Metasploit, virtuale |
| Previous by Thread: | Brutus, David Ball |
| Next by Thread: | Core Impact vs. Canvas vs. Metasploit, virtuale |
| Indexes: | [Date] [Thread] [Top] [All Lists] |