+- Hack Forums (https://hackforums.net)
+-- Forum: Hacks, Exploits, and Various Discussions (https://hackforums.net/forumdisplay.php?fid=45)
+--- Forum: Whitehat • Blue Team • Defensive Security (https://hackforums.net/forumdisplay.php?fid=448)
+---- Forum: Pentesting and Forensics (https://hackforums.net/forumdisplay.php?fid=231)
+---- Thread: Looking for Ideas - Technical Pentest Name on Intrusion via Enumeration (/showthread.php?tid=4702949)
Looking for Ideas - Technical Pentest Name on Intrusion via Enumeration - pwntoken - Feb 24, 2015
Okay, first off, it so happens that I was given a penetration test which were rejected by my lower vulnerability researchers (basically coming from the bug bounty family). As a part of my job role, I play by the team lead and anything which isn't intruded by the lower members on the organization is forwarded to me for a 'look-up' and intrude into the application.
Initially, I happen to enumerate deep into the application and publicly picked up some usernames left over on pastebin and tried their last name as the part of the password. Now this particular engagement gave me access to it's central system and I had everything from changing names, emails, roles, priviledges to access private customer data such as licenses and passport etc..
For me, as red team lead, I guess any intrusion via any method would be an valid attempt for a successfull penetration test. I am only confused with the part how this whole thing should be presented to the client since there were originally no vulnerabilities but violation of policies (password policies, user name creation policies, employee making their code public in pastebin policy, etc.). I need a technical name to present this issue infront of the client to get this escalated as soon as possible since in common terms, clients look forward to vulnerabilities and yet without using any vectors, I penetrated to their system.
What could be your thoughts over this? I look forward to teh community to help me get going with this. I appretiate your time and values for the same. Thank you. 🤝
* - Benign - Feb 25, 2015
Just present it as you would any vulnerability you'd found:
Overview of access gained
Detailed info of how you got in (discovered username in public domain, had weak password set to service x)
Suggest how you would remediate this issue (strong passwords, advise not using internal email addresses or usernames anywhere outside the corporate network etc.).
As a red team leader, have you not come across this before?
Edit: You could also specify the two items separately first: "Usernames discovered on public sites", then "Weak password set on user accounts" then combine them to present how they were used to get access to a given service.
* - pwntoken - Mar 2, 2015
(Feb 25, 2015 01:48 AM)Benign Wrote: Just present it as you would any vulnerability you'd found:
Overview of access gained
Detailed info of how you got in (discovered username in public domain, had weak password set to service x)
Suggest how you would remediate this issue (strong passwords, advise not using internal email addresses or usernames anywhere outside the corporate network etc.).
As a red team leader, have you not come across this before?
Edit: You could also specify the two items separately first: "Usernames discovered on public sites", then "Weak password set on user accounts" then combine them to present how they were used to get access to a given service.
A RTL doesn't have to mention/prepare the test reports. His only responsibility includes coordinating the testers in order to formulate and plan the assessment. Additionally I have to coordinate with the clients in order to deliver the technical details and a summary in general. In the absence of such testers (particular ones), I had to prepare his audit trails and summarize the executive report.
Either way, for what I see; this information should be in near future helpful to others and I am sharing this link here for purposes good to be delivered across. This below mentioned link would enlist all the details with which I was able to access the standard title charts:
Code
http://cwe.mitre.org/data/lists/2000.htmlI'd also include that bookmarking the aforementioned link is a must.