Your SlideShare is downloading. ×
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Privilege Escalation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Privilege Escalation

1,831

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,831
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Privilege Escalation Issue
  • 2. Nothing but a login
  • 3. Identified a Main.js file
  • 4. With some admin URL’s
    • https://www.site.com/Secure/Admin/AdminNewUser.aspx?user_id=spidynamics&pwd=pass
  • 5. A 302 to an inside page
    • HTTP/1.1 302 Object moved
    • Server: Microsoft-IIS/5.0
    • X-Powered-By: ASP.NET
    • Location: /Secure/ViewSystemMessage.aspx?id=47
    • Connection: Keep-Alive
    • Content-Length: 121
    • Content-Type: text/html
    • Cache-control: private
  • 6. Then get redirected again to a login
  • 7.  
  • 8. Let’s try accessing the admin functions
    • https://www.site.com/Secure/Admin/AdminUserProgramRole.aspx?uid=spidynamics
  • 9.  
  • 10.
    • https://www.site.com/Secure/Admin/AdminUserProgramRole.aspx?uid=2
  • 11.
    • UID field cycles thru each user
  • 12.
    • UID 3 is now another user
  • 13.
    • By incrementing the UID field to 183 – we identified our user id.
  • 14.
    • Clicking ‘Edit’ allowed us to set our user role to administrator
  • 15.  
  • 16.
    • By looking at the existing admin page names we knew about. A guess for the filename of admindefault.aspx turned up successful in the admin directory
  • 17.
    • When clicking on the URLs though it gave us a 404
  • 18.
    • So we started guessing – maybe it needs to be a .aspx extension?
  • 19. Success –just try adminusers.aspx

×