Skip to main content

security - SSL Subject Alternative Name and Man in the Middle attacks



My company "ourcompany" owns a 2nd level DNS domain name: ourcompany.org. We currently use this domain, as well as www.ourcompany.org and feature1.ourcompany.org, and have an SSL certificate generated for both these 3rd level domains.



Then we subscribed to a third party hosted service, hosted at ourcompany.thirdparty.org. They handle SSL and have a certificate whose subject is thirdparty.org and have the Subject Alternative Name *.thirdparty.org.




This 3rd party company also provides a functionality to add a custom domain. So we added a CNAME record in our DNS configuration, and now we have feature2.ourcompany.org pointing to ourcompany.thirdparty.org. Obviously at this point SSL is not working when accessing feature2.ourcompany.org.



Then the 3rd party company also asked us to ad TXT DNS entries to prove we are owners of the domain, and they were somehow able to update their SSL certificate and add the following Subject Alternative Names: ourcompany.org and *.ourcompany.org.




  • How is that not a potential source of Man in the Middle attack? (the 3rd party company can now impersonate us on any of our domains)

  • How can an arbitrary 3rd party company generate valid SSL certificates including SAN pointing to a domain they don't own? (their SAN include a lot more things than the CNAME domain record we added)

  • Did the certification authority allowed our domains as SAN because of the CNAME record pointing to their domain (in this case, how come the SAN included way more domains than just feature2.ourcompany.org), or because of the TXT entry (in this case, could someone point me to a resource explaining this process)?



Answer



After reviewing our DNS configuration, it seems that the certification authority validated the SAN entries in the 3rd party company certificate because of one of the TXT entries they asked us to add: globalsign-domain-verification=XXXXXXX, where XXXXXXX is a key provided by GlobalSign to the 3rd party company (documentation about this GlobalSign feature is hard to find but I could find something here). This answers the 2nd and 3rd questions.



As for the 1st one, it seems that the TXT entry being set to the 2nd level domain, the 3rd party company is now authorized to include the 2nd level domain as well as any 3rd level domain under it in the SAN entries of their certificate.


Comments

Popular posts from this blog

iLO 3 Firmware Update (HP Proliant DL380 G7)

The iLO web interface allows me to upload a .bin file ( Obtain the firmware image (.bin) file from the Online ROM Flash Component for HP Integrated Lights-Out. ) The iLO web interface redirects me to a page in the HP support website ( http://www.hp.com/go/iLO ) where I am supposed to find this .bin firmware, but no luck for me. The support website is a mess and very slow, badly categorized and generally unusable. Where can I find this .bin file? The only related link I am able to find asks me about my server operating system (what does this have to do with the iLO?!) and lets me download an .iso with no .bin file And also a related question: what is the latest iLO 3 version? (for Proliant DL380 G7, not sure if the iLO is tied to the server model)

linux - Awstats - outputting stats for merged Access_logs only producing stats for one server's log

I've been attempting this for two weeks and I've accessed countless number of sites on this issue and it seems there is something I'm not getting here and I'm at a lost. I manged to figure out how to merge logs from two servers together. (Taking care to only merge the matching domains together) The logs from the first server span from 15 Dec 2012 to 8 April 2014 The logs from the second server span from 2 Mar 2014 to 9 April 2014 I was able to successfully merge them using the logresolvemerge.pl script simply enermerating each log and > out_putting_it_to_file Looking at the two logs from each server the format seems exactly the same. The problem I'm having is producing the stats page for the logs. The command I've boiled it down to is /usr/share/awstats/tools/awstats_buildstaticpages.pl -configdir=/home/User/Documents/conf/ -config=example.com awstatsprog=/usr/share/awstats/wwwroot/cgi-bin/awstats.pl dir=/home/User/Documents/parced -month=all -year=all...

linux - How can I get my mediawiki to stop thinking I have cookies disabled?

I've searched half a day for how to resolve this issue, and can't figure it out. Shortly after I made my wiki a simple private wiki according to the instructions at Mediawiki's website, it started giving me this weird login error message: Wiki uses cookies to log in users. You have cookies disabled. Please enable them and try again. If I remove those private wiki settings, the error disappears, even if I try logging in. But I need it to be a private wiki for only my team. So what do I do? Here's what I've done so far. Just to be safe, after ever change, I try rebooting Apache using: sudo /etc/init.d/apache2 restart In my php.ini file, I have the following set: session.save_path = "/var/lib/php5" session.cookie_secure = secure session.cookie_path = /tmp session.cookie_domain = my server's internal URL (should I even set this? this field was blank before, but not commented out) session.referer_check = Off I ran the following to ensure that the fold...