Archive

Archive for the ‘Internet, Unix en security’ Category

I passed my CISSP exam

January 7th, 2012 No comments

Last December 10th I took the CISSP exam in Brussels and yesterday after only four weeks I received the following in my mailbox:

Dear Hans Spaans:

Congratulations! We are pleased to inform you that you have passed the Certified Information Systems Security Professional (CISSP®) examination – the first step in becoming certified as a CISSP.

So I now only need to submit my resume and endorsement. Ow and order some cake for co-workers. And the reason I did it in Brussels instead of Utrecht? I was a little bit late with requesting the exam as I did that on November 23th. Now it is time to plan the next exam, but it won’t be CEH.

Tags: (ISC)^2, CISSP

Implementing RFC 2142 for beginners

January 6th, 2012 No comments

I stumbled on a phishing site for a Dutch-bank in my junk-folder and for once I decided to have closer look to see if the filter was working correctly. Is was, but after reviewing the phishing site I saw two things and it was time to act.

The first one was the hosting service. It was a free hosting service so no defacing or whatever. That makes live very convenient for hosting a phishing site that looks pretty safe. The seconds was the use of a free hosting service for submit and collect forms. The funny part is btw, that the seconds appears to very if a certain tag is in the referral page, but doesn’t check if it really shows up. So to eliminate the inclusion in the webpage, the have added then after the closing HTML-tag. Maybe using XPath was a better design choice over just search for a certain string to enable the service.

As the form was asking for all kind of funny details to do perfect phishing I decide to report this to all involved parties. The site being phished, Rabobank in this case, the hoster T15.org and Formbuddy for processing phishing data. After so checking and didn’t found enough leads on alternative mail-addresses to report this I decide to use RFC 2142 reserved mail-addresses and the following happend.

<abuse@rabobank.nl>: host mail01.rabobank.nl[145.72.107.42] said: 550 #5.1.0
Address rejected. (in reply to RCPT TO command)

<security@rabobank.nl>: host mail01.rabobank.nl[145.72.107.42] said: 550 #5.1.0
Address rejected. (in reply to RCPT TO command)

<security@formbuddy.com>: host ASPMX.L.GOOGLE.com[74.125.79.27] said: 550-5.1.1
The email account that you tried to reach does not exist. Please try
550-5.1.1 double-checking the recipient’s email address for typos or
550-5.1.1 unnecessary spaces. Learn more at
550 5.1.1 http://mail.google.com/support/bin/answer.py?answer=6596
d15si7088885eei.16 (in reply to RCPT TO command)

The one that worries me the most is that a bank appears to have no working mail-addresses as described in Section 4 of RFC 2142. Those are basically key for contacting parties in case of emergencies or trouble. The abuse-reject was already noticed by someone last year, but I really wonder how a /16 network can ignore this. Also since there is no abuse-c entry know for there /16.

Update 2012-01-06: The nice guys at T15.org have taken the website down within a few hours after reporting.

Faulty RSS-feeds

December 30th, 2011 2 comments

Taking a look at some logs from a RSS-collector two things raised my eyebrows. The first is how many feeds are being served by FeedBurner instead of directly being served by the website it self. The part that worries me is that a lot of those feeds also are about security, privacy and compliance. I think a lot of those people have something to think about in 2012.

The other thing that worries me even more is something I discussed with WordPress developers a couple of years ago and I know others who have done the same with other projects. A lot of projects learned to do input validation, but most of them still need to learn to do output validation. The parser I currently use appears to be very strict luckily and drops a feed when it doesn’€™t parse correctly. Here comes the funny part, other parses like from Google Reader seems to be more forgiving.

When I search for “libxml exploit” on Google Search I get 1.220.000 results back. I didn’t start searching for parsers currently in use, but this doesn’t look very promising. With current hash-issues in mind, how could this be used to be an attack vector? Keep in mind that a lot of sites use FeedBurner to take the load of there site. And yes, FeedBurner doesn’t really clean things up if I may believe my current logs. So the recipe looks like a good exploit to misuse, a high profile WordPress based website with FeedBurner enabled and watch the fireworks.

So maybe it is a good idea for 2012 to see if the parser I’m currently using is up to standard. This can become nasty very quickly if things go wrong. Maybe also a note to others, output validation matters together with input validation. The JavaScript-alert is still a funny one to deploy on websites.

Another company switching to XMPP

December 29th, 2011 2 comments

Back in 1996 ICQ saw it first light and instant messaging was born and it took Microsoft until 1999 before MSN Messenger was launched. Two proprietary protocols for instant messaging with closed specifications. Also a third protocol was started in 1998 under the name Jabber which was renamed as XMPP a few years later. Long time it was labeled as “only for geeks” or “something for Linux-users”.

This all changed in 2005 as Google launched Google Talk which was based on XMPP and also allowed server-to-server communication 2006 so Google Talk users could communicate with users outside the Google netwerk. Other services like audio and video where added in the years after. This forced others to rethink there ideas about there instant messaging network where Facebook Chat followed the same strategy as Google Talk. Shortly after AOL started experimenting with ICQ over XMPP in 2008.

The last big bastion was Live Messenger from Microsoft, but recently it was announced that also Microsoft started to offer an XMPP API to there instant messaging network. Meaning people with an XMPP client could use the Microsoft instant messaging network without any additional software. Telepathy developers from Freedesktop.org directly jumped in and trying to get it in with GNOME 3.4 together with better Facebook support like it is now for Google in GNOME Online Accounts. With this the only question remains if Microsoft for example will also allow server-to-server communication like Google.

Now that we slowly moving towards an unified communications standard where companies as Cisco are pushing for, we also see a simplification and reduction of standards in use. Hopefully Debian can drop in the release after Wheezy all packages that depend on the old Messenger protocol. Also hopefully Microsoft will also jump into the bandwagon for standardized calendar en contacts support, but time will tell. For now it is a plus 1 for open and free standards.

Usenet, goodbye and thanks for all the fish

December 27th, 2011 No comments

After being an usenet junky for a long time the time came that I switched from being a regular poster to a lurker. I still followed a lot of groups for many years until I realised that I only was syncing my newsspool for at least 12 to 18 months without any reading. After some catching up on some groups I saw that I wasn’t the only person. A lot of groups in the nl-tree are just empty or mostly abandoned or they contained mostly spam. Other trees like the comp-tree has more posters, but also a lot more spam and I mean really a lot more.

I still think usenet is a good platform and that it has served it’s purpose. Due to it’s openness as a platform it also lead to a lot of people abusing it and it is unforgiving. One thing that companies like Microsoft, but also XS4ALL are switching to privately hosted forums where they can control the posters and the content. This leaves certain mailinglists for me to follow, but even that number has been reduced as most of them have the Eternal September feeling. So everyone thanks for all the time and discussions on Usenet and hopefully we meet again.

Stop SOPA