USN-2697-1: Ghostscript vulnerability

Ubuntu Security Notice USN-2697-1

30th July, 2015

ghostscript vulnerability

A security issue affects these releases of Ubuntu and its
derivatives:

  • Ubuntu 15.04
  • Ubuntu 14.04 LTS
  • Ubuntu 12.04 LTS

Summary

Ghostscript could be made to crash or run programs if it processed a
specially crafted file.

Software description

  • ghostscript
    – PostScript and PDF interpreter

Details

William Robinet and Stefan Cornelius discovered that Ghostscript did not
correctly handle certain Postscript files. If a user or automated system
were tricked into opening a specially crafted file, an attacker could cause
a denial of service or possibly execute arbitrary code.

Update instructions

The problem can be corrected by updating your system to the following
package version:

Ubuntu 15.04:
libgs9

9.15+dfsg-0ubuntu2.1
Ubuntu 14.04 LTS:
libgs9

9.10~dfsg-0ubuntu10.4
Ubuntu 12.04 LTS:
libgs9

9.05~dfsg-0ubuntu4.3

To update your system, please follow these instructions:
https://wiki.ubuntu.com/Security/Upgrades.

In general, a standard system update will make all the necessary changes.

References

CVE-2015-3228

USN-2698-1: SQLite vulnerabilities

Ubuntu Security Notice USN-2698-1

30th July, 2015

sqlite3 vulnerabilities

A security issue affects these releases of Ubuntu and its
derivatives:

  • Ubuntu 15.04
  • Ubuntu 14.04 LTS
  • Ubuntu 12.04 LTS

Summary

SQLite could be made to crash or run programs if it processed specially
crafted queries.

Software description

  • sqlite3
    – C library that implements an SQL database engine

Details

It was discovered that SQLite incorrectly handled skip-scan optimization.
An attacker could use this issue to cause applications using SQLite to
crash, resulting in a denial of service, or possibly execute arbitrary
code. This issue only affected Ubuntu 14.04 LTS. (CVE-2013-7443)

Michal Zalewski discovered that SQLite incorrectly handled dequoting of
collation-sequence names. An attacker could use this issue to cause
applications using SQLite to crash, resulting in a denial of service, or
possibly execute arbitrary code. This issue only affected Ubuntu 14.04 LTS
and Ubuntu 15.04. (CVE-2015-3414)

Michal Zalewski discovered that SQLite incorrectly implemented comparison
operators. An attacker could use this issue to cause applications using
SQLite to crash, resulting in a denial of service, or possibly execute
arbitrary code. This issue only affected Ubuntu 15.04. (CVE-2015-3415)

Michal Zalewski discovered that SQLite incorrectly handle printf precision
and width values during floating-point conversions. An attacker could use
this issue to cause applications using SQLite to crash, resulting in a
denial of service, or possibly execute arbitrary code. (CVE-2015-3416)

Update instructions

The problem can be corrected by updating your system to the following
package version:

Ubuntu 15.04:
libsqlite3-0

3.8.7.4-1ubuntu0.1
Ubuntu 14.04 LTS:
libsqlite3-0

3.8.2-1ubuntu2.1
Ubuntu 12.04 LTS:
libsqlite3-0

3.7.9-2ubuntu1.2

To update your system, please follow these instructions:
https://wiki.ubuntu.com/Security/Upgrades.

In general, a standard system update will make all the necessary changes.

References

CVE-2013-7443,

CVE-2015-3414,

CVE-2015-3415,

CVE-2015-3416

USN-2699-1: HPLIP vulnerability

Ubuntu Security Notice USN-2699-1

30th July, 2015

hplip vulnerability

A security issue affects these releases of Ubuntu and its
derivatives:

  • Ubuntu 15.04
  • Ubuntu 14.04 LTS
  • Ubuntu 12.04 LTS

Summary

HPLIP could be tricked into downloading a different GPG key when
performing printer plugin installations.

Software description

  • hplip
    – HP Linux Printing and Imaging System (HPLIP)

Details

Enrico Zini discovered that HPLIP used a short GPG key ID when downloading
keys from the keyserver. An attacker could possibly use this to return a
different key with a duplicate short key id and perform a man-in-the-middle
attack on printer plugin installations.

Update instructions

The problem can be corrected by updating your system to the following
package version:

Ubuntu 15.04:
hplip-data

3.15.2-0ubuntu4.2
Ubuntu 14.04 LTS:
hplip-data

3.14.3-0ubuntu3.4
Ubuntu 12.04 LTS:
hplip-data

3.12.2-1ubuntu3.5

To update your system, please follow these instructions:
https://wiki.ubuntu.com/Security/Upgrades.

In general, a standard system update will make all the necessary changes.

References

CVE-2015-0839

USN-2700-1: Linux kernel vulnerabilities

Ubuntu Security Notice USN-2700-1

30th July, 2015

linux vulnerabilities

A security issue affects these releases of Ubuntu and its
derivatives:

  • Ubuntu 14.04 LTS

Summary

Several security issues were fixed in the kernel.

Software description

  • linux
    – Linux kernel

Details

Andy Lutomirski discovered a flaw in the Linux kernel’s handling of nested
NMIs (non-maskable interrupts). An unprivileged local user could exploit
this flaw to cause a denial of service (system crash) or potentially
escalate their privileges. (CVE-2015-3290)

Andy Lutomirski discovered a flaw that allows user to cause the Linux
kernel to ignore some NMIs (non-maskable interrupts). A local unprivileged
user could exploit this flaw to potentially cause the system to miss
important NMIs resulting in unspecified effects. (CVE-2015-3291)

Andy Lutomirski and Petr Matousek discovered that an NMI (non-maskable
interrupt) that interrupts userspace and encounters an IRET fault is
incorrectly handled by the Linux kernel. An unprivileged local user could
exploit this flaw to cause a denial of service (kernel OOPs), corruption,
or potentially escalate privileges on the system. (CVE-2015-5157)

Update instructions

The problem can be corrected by updating your system to the following
package version:

Ubuntu 14.04 LTS:
linux-image-3.13.0-61-generic-lpae

3.13.0-61.100
linux-image-3.13.0-61-lowlatency

3.13.0-61.100
linux-image-3.13.0-61-powerpc-e500mc

3.13.0-61.100
linux-image-3.13.0-61-powerpc64-emb

3.13.0-61.100
linux-image-3.13.0-61-powerpc64-smp

3.13.0-61.100
linux-image-3.13.0-61-powerpc-e500

3.13.0-61.100
linux-image-3.13.0-61-generic

3.13.0-61.100
linux-image-3.13.0-61-powerpc-smp

3.13.0-61.100

To update your system, please follow these instructions:
https://wiki.ubuntu.com/Security/Upgrades.

After a standard system update you need to reboot your computer to make
all the necessary changes.

ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed. If
you use linux-restricted-modules, you have to update that package as
well to get modules which work with the new kernel version. Unless you
manually uninstalled the standard kernel metapackages (e.g. linux-generic,
linux-server, linux-powerpc), a standard system upgrade will automatically
perform this as well.

References

CVE-2015-3290,

CVE-2015-3291,

CVE-2015-5157

USN-2701-1: Linux kernel (Trusty HWE) vulnerabilities

Ubuntu Security Notice USN-2701-1

30th July, 2015

linux-lts-trusty vulnerabilities

A security issue affects these releases of Ubuntu and its
derivatives:

  • Ubuntu 12.04 LTS

Summary

Several security issues were fixed in the kernel.

Software description

  • linux-lts-trusty
    – Linux hardware enablement kernel from Trusty

Details

Andy Lutomirski discovered a flaw in the Linux kernel’s handling of nested
NMIs (non-maskable interrupts). An unprivileged local user could exploit
this flaw to cause a denial of service (system crash) or potentially
escalate their privileges. (CVE-2015-3290)

Andy Lutomirski discovered a flaw that allows user to cause the Linux
kernel to ignore some NMIs (non-maskable interrupts). A local unprivileged
user could exploit this flaw to potentially cause the system to miss
important NMIs resulting in unspecified effects. (CVE-2015-3291)

Andy Lutomirski and Petr Matousek discovered that an NMI (non-maskable
interrupt) that interrupts userspace and encounters an IRET fault is
incorrectly handled by the Linux kernel. An unprivileged local user could
exploit this flaw to cause a denial of service (kernel OOPs), corruption,
or potentially escalate privileges on the system. (CVE-2015-5157)

Update instructions

The problem can be corrected by updating your system to the following
package version:

Ubuntu 12.04 LTS:
linux-image-3.13.0-61-generic

3.13.0-61.100~precise1
linux-image-3.13.0-61-generic-lpae

3.13.0-61.100~precise1

To update your system, please follow these instructions:
https://wiki.ubuntu.com/Security/Upgrades.

After a standard system update you need to reboot your computer to make
all the necessary changes.

ATTENTION: Due to an unavoidable ABI change the kernel updates have
been given a new version number, which requires you to recompile and
reinstall all third party kernel modules you might have installed. If
you use linux-restricted-modules, you have to update that package as
well to get modules which work with the new kernel version. Unless you
manually uninstalled the standard kernel metapackages (e.g. linux-generic,
linux-server, linux-powerpc), a standard system upgrade will automatically
perform this as well.

References

CVE-2015-3290,

CVE-2015-3291,

CVE-2015-5157

Mr. Robot Review: br4ve-trave1er.asf

This week’s episode of Mr. Robot was an exciting one for us here at Avast – our product made an appearance on the show! In addition to the exploit Avast blocked, there were many other interesting hacks in this week’s episode, which I discussed with Avast security experts, Filip Chytry and Jiri Sejtko.

Mr_Robot_02

Minute 7:00: Elliot is in his apartment with Isaac and DJ. Something about Vera’s brother, Isaac, bugs Elliot and what does Elliot do when he is bugged by someone? He hacks them!

Stefanie: We see Elliot once again turn to the Linux distribution, Kali, to hack Isaac’s cell phone. He seems to do this within a matter of seconds, how easy is this to do?  Later on, when Elliot visits Vera in prison, we learn what Elliot plans to auto-send information from Isaac’s phone to himself. This seems really intrusive and couldn’t Isaac just get a new phone?

Filip Chytry: This is a more advanced hack and unless Elliot had everything prepped before they entered his apartment, this would taken a lot more time to execute (but this is a TV show, so things sometimes happen faster on TV then they do IRL). The Linux distribution Kali, a popular tool for penetration testing, can be used to plant code on a device. But, Isaac’s phone would have had to be connected to either Elliot’s Wi-Fi network or Elliot could have set up a fake Wi-Fi hotspot using a popular network name like “Starbucks Wi-Fi” or “ATT Wi-Fi”, a Wi-Fi network Isaac’s phone had connected to before and would connect to automatically. Elliot would then use Kali to exploit a vulnerability in Isaac’s phone and plant code to send information from the phone to Elliot’s chosen destination. Since Elliot told Vera about this, Vera could have told Isaac and Isaac could have gotten a new phone, but Isaac was not given a happy end in this episode…

Minute 11:30: Elliott tries to find a way to hack into the prison’s network. Darlene helps him by uploading an exploit onto USB sticks. The USB sticks are branded with E-Corp’s logo, to look trustworthy. She drops the USB sticks on the prison’s parking lot. A police officer takes one of the sticks and inserts it into his work PC. First, a window appears saying “get your free $100 eTunes gift card”, and then a window asking him what his favorite music genre is appears. He clicks through several questions – and then BAM! Avast detects the exploit!

Mr_Robot_03

Stefanie: Watching this scene, we couldn’t be prouder. Avast detects an exploit in Mr. Robot, this is so exciting! Taking a closer look at Avast’s warning pop-up, we can see the exploit was a Trojan: JS:ScriptPE-inf (Trj) Is this actually a Trojan that exists or is this made up?

Jiri: This is a real detection. The detection is triggered by an HTML or Javascript file that contains a URL that Avast blocks, as it includes a malicious file. It is, however, hard to say what the URL contained. I would expect it to be some kind of exploit that tries to exploit a vulnerability on the officer’s machine, in order to execute code that would give Elliot access to the prison network.

Minute 31:38: Elliot runs an undetectable activated signal sniffer that will locate any wireless signal in sight on his phone while it is at the prison’s security desk. When Elliot exits the prison, he checks the data retrieved from the sniffer and is disappointed to see that the prison’s network uses WPA2 encryption.

Stefanie: Elliot mentions that WPA2 is “borderline unhackable” and then he mentions a handshake? Is WPA2 encryption really that secure and what handshake is he referring to?

Filip: WPA stands for Wi-Fi Protected Access and WPA2 is WPA’s successor, which uses AES (Advanced Encryption Standard). WPA is the best encryption currently available for Wi-Fi, so when Elliot says it is border line unhackable, he means it! There is one way WPA2 can be hacked, but, as Elliot mentions, it takes a long time to do. When a client connects to an access point, a four-way handshake happens, encrypting messages to confirm that both parties know the so called PSK (pre-shared key) and PMK (pairwise master key), without revealing them. In order to hack a WPA2 protected network, you have to capture and decrypt the authentication handshake. Capturing the handshake can be easy but the decryption can be difficult, depending on the Wi-Fi network’s password complexity. 

After Elliot gives up on the idea of hacking into the prison’s Wi-Fi, a police car drives by and automatically connects to his smartphone. He says “The mobile feed on the cameras… I don’t need to hack WPA when there is dedicated 4G”. Later, in minute 35:40, we see Elliot hacking a police patrol car. His plan is to connect to the “patrol car’s bluetooth to run the exploit on the PLC”. He is successful and gives the order “at 9:49, all the cell doors should open”.

Stefanie: What’s a PLC?

Jiri: PLC stands for “programmable logic controller”, it’s a computer usually used in industrial environments. The most famous PLC attack vector is probably Stuxnet, which was designed to monitor Siemens machines in Iranian nuclear facilities and manipulate the centrifuge’s rotor speed.

Stefanie: In the case of Mr. Robot, the PLC is used in the prison to control the locks of the cell doors.

Jiri: Yes, PLC-based systems are heavily used in prisons, there are prisons in the U.S., where PLCs control over 900 doors. Security researchers have mentioned concerns about prison PLC systems’ vulnerabilities already years ago and Sam Esmail, the producer and writer of Mr. Robot, cleverly ties these concerns into the story. Potential exploits are also presented in the open source Metasploit Framework, which is a tool for developing and executing exploit code – so basically, every script kiddie can (ab)use it.

Stefanie: Sounds scary. How could a PLC be protected from an exploit?

Jiri: System administrators should make sure that the PLC firmware and controlling software is patched and always updated. They should also use proper network segmentation to prevent access to the PLC network from other local networks – air gaps – like the one in Mr. Robot, where the PLC could be accessed via patrol car’s laptop. Also, physical media like USB flash disks and mobile phones should be restricted from accessing the PLC.

Stefanie: Sounds pretty simple in a way… Has anyone ever broken out of prison by hacking into the prison’s system?

Filip: There are many ways prisoners can use technology to “hack” themselves out of prison. Earlier this year, a criminal imprisoned in a jail near London, managed to escape the prison using social engineering. He set up a fake web domain that resembled the domain of the court responsible for him. He then used this domain in an email he sent to the prison’s custody inbox, including the message that he should be released. His escape was noticed only three days later, when solicitors were supposed to interview him.

The (cyber)criminal was caught again some time later, but this story shows that a jailbreak via “hack” isn’t that unrealistic in today’s world.

Mr. Robot airs on Wednesdays at 9/10 central on USA

via: USA Networks Mr. Robot airs on Wednesdays at 9/10 central on USA

Thank you Jiri and Filip for taking the time to discuss this week’s Mr. Robot hacks!

What did hack did you find most interesting from the episode? Let us know in the comments below :)

 

Routers are set to become the digital battleground of the future

By now, most of us are familiar with the term the “Internet of Things”. It has come to describe the always on, always connected world where day to day objects are online. It ranges from smart-watches to smart fridges and is closer to reality than you may think.

Much has been written about the need to secure the devices that make up the Internet of Things, but I believe there is another battle to be won.

According to most reliable research, the number of Internet connected devices is growing rapidly and will continue to do so for the foreseeable future.

IoT Devices

 

Building security into each and every one of these devices is no mean feat. In fact, it will be very difficult indeed. That’s what I believe that it is of vital importance that we focus our attention on securing routers and Wi-Fi hotspots.

As the number of Internet enabled devices in our homes continues to increase, more and more members of the public are getting ready to adopt smart home appliances, energy meters and wearables.

Connected Devices

 

All of these newly connected devices entering the home should be rigorously secured as they will be handling data specific to your household. Securing them individually could be tough though, until you realise that they share something in common – they communicate via the Internet access point, a home router.

As you can see, the number of home routers in the market is continuing to grow rapidly, but is only a fraction of the number of total devices.

Private Hotspots

 

Robustly securing each home router or a public hotspot has the knock-on effect of securing the data transmission of dozens of devices and, for my money, is a much more realistic approach to securing the Internet of Things.

Sadly, security on most popular routers is still pretty basic and has a user experience to match. Clunky menus that aren’t immediately intuitive can leave users at a loss when it comes to making changes to their Internet settings.

Here are three simple things that you can do right now to help improve the security of your home Wi-Fi network.

 

Three steps to securing your home router:

Change the login details

Most routers will come with default login details. Many people never get round to changing them but you really should. “User name: admin Password: Password” is not a secure login and could potentially grant router level access to attackers if they know the manufacturer defaults of your device.

Set up an access list:

Most routers will allow you to set up a “permitted devices” list that limits access to your network. Setting this list up and including all your family’s devices is a good way to make sure that no unauthorized devices access your network.

Double check your Firewall

A Firewall is an important router feature that helps filter out bad traffic requests coming into your home. All traffic that is sent and received in your home goes through a Firewall and more specifically through “ports”. These are akin to doors, with each one dedicated to certain traffic types. It is always worth checking your Firewall settings in your router to make sure that you do not have any unnecessarily opened ports.

 

For tips on how to improve your home Wi-Fi Signal, check out the video below.

The Value of an Unplugged Vacation

In keeping with tradition, each year my husband Bob and I gather some of our 14 nieces and nephews and do an annual diving trip. Generally we provide diving lessons to each of the children as they come of age. This year, we did an “alumni” trip for all of the kids who have participated before.

It was truly awesome – and all about diving, eating and sleeping and, then… repeat.

We also had a no-devices-allowed policy. So each evening we had dinner at the big pagoda on the beach. Afterwards, all of us in hammocks. And every night we had amazing conversations!

I was most struck by my young nieces and nephews’ views on how nice it was to be unplugged… Thoughts on how intrusive the internet and smart devices have become in their young lives…I.e. If you don’t text back in real-time, you could lose a friend who thinks you are being unresponsive… (Sound familiar?)

But they really reveled in the opportunity to get away from it all. It wasn’t just me, but kids!

It started me thinking in general about the value of vacations, but especially unplugged ones.

The benefits of taking a vacation are well documented, and practical. Pluses include higher productivity, improved morale, better employee retention, and a better overall workplace culture. That’s just in the workplace. The health benefits for the individual are evident too and should concern all of us.

Numerous studies have shown that vacations lower blood pressure and ease depression…and that even looking forward to a vacation brings major dividends. In just one example, the widely regarded Framingham Heart Study, a long-term ongoing cardiovascular study that began in 1948 to analyze adult subjects who were at risk of heart disease, found a positive correlation between more frequent vacations and longer healthier lives.

But did you know that more than 40% of American workers who received paid time off did not take all of their allotted time in 2013—even despite the obvious personal benefits? This is according to the most recent study entitled “An Assessment of Paid Time Off in the U.S.” commissioned by the U.S. Travel Association, a trade group, and completed by Oxford Economics. The study found, among other things, that we as workers left an average of 3.2 paid time off days unused in 2013, which adds up to 429 million unused days off.

The fact is many people who don’t take vacations are not only hurting themselves and their own productivity. They’re also hurting our country’s economy. And in terms of the overall economy, the Oxford/USTA study found that if employees would take just one additional day of earned leave each year, the result would mean $73 billion in output for the U.S. economy and positive impacts for both employees and businesses.

It has lead to some innovative workplace policies. One of the most intriguing is a Denver-base tech company’s Paid Paid Vacation policy. Bart Lorang, co-founder and CEO of the Denver-based tech company FullContact introduced “Paid Paid Vacation” in 2012. In addition to the standard 15 days paid vacation plus federal holidays (allotted by many US companies), the company gives employees $7,500 to finance a trip. That’s cash on top of their full salaries. The concept is both generous and innovative by US standards!

There is a caveat, however. The employees have to agree to three rules:

  • No checking works emails, texts, or calls.
  • No working, period.
  • You have to actually go on vacation or you don’t get the money.

 

According to FullContact, the program has translated into real-life benefits.

For example, FullContact’s communications director Brad McCarty told the Washington Post, “The really big names in tech all focus on the same idea, that employee happiness has to come before everything else. While it’s really difficult to measure that return on investment from a dollar standpoint, it’s not difficult to measure what happens when someone returns from a Paid Paid Vacation: you see, without fail, people shining brighter, working harder and more excited to get back into the swing of things.” There also are other ancillary benefits, as Lorang told the Business Insider.

Of note: because the employee who is going on vacation is literally cut-off from work, it’s essential that other employees are cross-trained or up-to-speed on the vacationee’s projects. This means sharing information and avoiding the ‘hero’ trap – the “I’m the only one that can do this” mentality…

Perhaps best of all, and an inspiration for other small business owners, is that Lorang takes his own advice and has an unplugged vacation at least once a year.

I know that we are all very busy and engaged with our work and our daily lives. And our schedules are always overbooked. But please do take the time to have some fun, unplug, or have an adventure by yourself and/or with your loved ones. You’ll find yourself coming back to work with a smile on your face!

Here’s a shout out and “miss you” to all my nieces and nephews, who seem to be learning this at an early age! Inspiring.J