4 ms·
Interestingly enough, despite malaysia airlines claiming that this is just a DNS hijack. It appears that their own CDN (Akamai) is now serving the deface page.
by ryanlol 12y ago
Interestingly enough, despite malaysia airlines claiming that this is just a DNS hijack. It appears that their own CDN (Akamai) is now serving the deface page. (The page was being served by cloudflare before)
- JoshTriplett 12y agoMany CDNs work by retrieving the page themselves, caching it, and re-delivering on request. In that case, if the original page changes, the CDN would automatically change too.
- ryanlol 12y agoWhich would imply that their backend was compromised, not just DNS.
- zkhalique 12y agoThe CDN could have simply refreshed its DNS cache couldn't it? That would mean it loaded the files from somewhere else.
- ryanlol 12y agoUnless there was something horribly wrong with their setup, akamai would have prevented that from happening.
- Tiksi 12y agoI'm not sure how they are supposed to prevent this. If you have access to the dns, you can change the record for the origin server that the cdn pulls from. Nothing "horribly wrong" with that.
- ryanlol 12y agoAkamai makes you to set your own DNS server for it to pull records from, the domain getting hijacked should not have any effect on what that DNS server is returning.
- Tiksi 12y agoI may be missing something, but this: >It added that its domain name system was compromised. sounds like their DNS server was compromised. Also, I've never worked with Akamai, but every cdn I have worked with just follows the ns records and resolves against that, which could be changed with access to the domain/registrar. Does Akamai not do that?
- ryanlol 12y agoTheir domains DNS servers were switched to cloudflare, I'd imagine that's the DNS compromise they're referring to. Not _their_ DNS servers getting compromised.
- Tiksi 12y agoHmm, I figured it was just the records being pointed to cloudflare, since everything I could find makes it sound like that, but you may be correct that the nameservers were changed, as cloudflare's nameservers look like they have a record for the domain, but are returning different records: http://paste.click/s/qKkejf http://paste.click/s/qKkejf [0] Which appears to be down now anyways: http://paste.click/s/UlxsWA http://paste.click/s/UlxsWA [1] However I suspect cloudflare's nameservers might just return A records pointing to cloudflare if they don't exist, I'm not sure. Though that still doesn't answer the second part. Would Akamai not use the authoritative nameservers to resolve the origin? Cdn providers I've worked with (Level3, edgecast, Highwinds, and others) just resolve based on the authoritative nameservers, and I'm genuinely curious if Akamai doesn't do that. Edit: forgot that my keybinding throws the js/syntax highlighted url into my clipboard, which is pointless for this, here are the plaintext links to the same thing: [0] http://paste.click/qKkejf http://paste.click/qKkejf [1] http://paste.click/UlxsWA http://paste.click/UlxsWA