Internationalization and the Internet

The Internet is a child of the United States of America, so it does not come as a surprise that only Latin letters and some scientific characters were used when the systems and the software (then called ARPANET) were designed. In today’s world, where roughly half the global population, with its different letters and alphabets uses the Internet, things look different.

The Need for Internationalization

You might have seen a so-called IDN before. IDN stands for internationalized domain name and all it boils down to, is a web address with special characters. This can be of great help for Internet users that live in regions where the primary alphabet in use is not Latin-based or is extended with special characters. Take Swedish for instance: the letters ä, ö and å augment the standard Latin alphabet. Without the support of IDNs, you would have to agree on a different (Latin) character for domains – like a or aa instead of å. Instead of visiting the website of your favorite Swedish bakery with www.pågen.se, you would have to go to www.pagen.se. This is okay until another company with the name Pagen appears and wants to claim that domain name. It becomes confusing very quickly for the visitors.

Wait…IDN what?

The Domain Name Service (short: DNS), which is used to translate a web address to something the computer understands, only accepts Latin characters. To make internationalized domains work, a system called punycode is used. A complete explanation of the algorithm is way out of scope for this article, but here is a short one. Whenever you enter an address like pågen.se, punycode prepends xn--, skips all non-Latin characters of the domain (å) and appends a dash to the remaining characters (pgen). So far, the result is xn--pgen-. Now, some black magic (finite state machines and generalized variable length integers) is used to represent the location and the identity of the skipped characters. In the end, the result looks like xn--pgen-qoa.se. This is the domain that your browser will access. You, as a user, will not feel any difference as this is done transparently by your browser. Arguably the first internationalized domain (rather subdomain in this case) was http://räksmörgås.josefsson.org.

How it affects you?

There are alphabets which contain letters similar to the ones in other alphabets. Take the Cyrillic script for instance: the Cyrillic letter а resembles the Latin character a. In a so-called IDN homograph attack, a cyber-criminal uses exactly this resemblance to mimic trusted websites. Imagine the domain in the following pictures.

Internationalized version of a domain. The first a is Cyrillic, not Latin

Internationalized version of a domain. The first a is Cyrillic, not Latin

From the looks of it, it is paypal.com. You would almost have to be psychic to note that the first a is a Cyrillic letter. Now the attacker only needs to design a page that looks exactly like PayPal’s and send the login credentials to his or her email address – Mission accomplished.

If the domain is considered suspicious, modern browsers will show the punycoded variant

If the domain is considered suspicious, modern browsers will show the punycoded variant

Not all is lost

Fortunately, it is not that simple to deceive unsuspecting users anymore. Modern day browsers indicate that you are browsing an internationalized website as the image below shows.

Internationalization feature of Internet Explorer: shows a small icon in the address bar

Internationalization feature of Internet Explorer: shows a small icon in the address bar

In contrast to typosquatted URLs, where you might be able to spot phishy URLs by looking at them twice, IDNs can pose a real problem. You have to rely even more on a strong Web protection. It shows that common sense does not protect you from everything on the Internet and that it is crucial to have an up-to-date antimalware solution on all your devices.

Recommended Reading & Resources

Internationalized Domain Name
Punycode
Internet Usage Statistics
Internet
Homograph Attack
DNS

The post Internationalization and the Internet appeared first on Avira Blog.

Digital Invasion: 3 things we learned from CES 2015

Ever lost a kid somewhere? Not anymore if the gadget vendors have anything to say about it. Now you can digitally strap your kid to your tablet and keep track of them. Kids not running enough to stay trim? There’s an app for that that works the same way. Got high blood sugar? You can keep track of that too using the sensor-du-jour highlighted at CES 2015 in Las Vegas.

The post Digital Invasion: 3 things we learned from CES 2015 appeared first on We Live Security.

Facebook privacy – why statements about copyright don’t do anything

Facebook users around the world have reported the return of the network’s longer-lasting hoaxes – a legal disclaimer which allows users to regain copyright over their images and other content. Here’s why it doesn’t work.

The post Facebook privacy – why statements about copyright don’t do anything appeared first on We Live Security.

Fedora 20 Security Update: cross-binutils-2.25-3.fc20

Resolved Bugs
1162577 – CVE-2014-8501 cross-binutils: binutils: out-of-bounds write when parsing specially crafted PE executable [fedora-all]
1162601 – CVE-2014-8502 cross-binutils: binutils: heap overflow in objdump [fedora-all]
1162611 – CVE-2014-8503 cross-binutils: binutils: stack overflow in objdump when parsing specially crafted ihex file [fedora-all]
1162625 – CVE-2014-8504 cross-binutils: binutils: stack overflow in the SREC parser [fedora-all]
1162659 – cross-binutils: binutils: directory traversal vulnerability [fedora-all]
1162672 – cross-binutils: binutils: out of bounds memory write [fedora-all]<br
Upgrade to binutils-2.25 thus fixing a number of security bugs

Fedora 20 Security Update: docker-io-1.4.1-4.fc20

Resolved Bugs
1180059 – SELinux is preventing /usr/bin/docker from ‘getattr’ accesses on the file /.docker/key.json.
1173324 – CVE-2014-9357 CVE-2014-9356 CVE-2014-9358 docker-io: various flaws [fedora-all]
1172782 – CVE-2014-9357 docker: Escalation of privileges during decompression of LZMA archives
1172761 – CVE-2014-9356 docker: Path traversal during processing of absolute symlinks
1172787 – CVE-2014-9358 docker: Path traversal and spoofing opportunities presented through image identifiers<br
allow unitfile to use /etc/sysconfig/docker-network
Security fix for CVE-2014-9357, CVE-2014-9358, CVE-2014-9356