Monthly Archives: December 2014
Google Considers Warning Internet Users About Data Risks
Sony Sued By Ex-Staff Over Draft Security, Leaked Privates
Sony Cancels Premiere Of The Interview After Hacker Terrorist Threats
Container Security: Isolation Heaven or Dependency Hell
Docker is the public face of Linux containers and two of Linux’s unsung heroes: control groups (cgroups) and namespaces. Like virtualization, containers are appealing because they help solve two of the oldest problems to plague developers: “dependency hell” and “environmental hell.”
Closely related, dependency and environmental hell can best be thought of as the chief cause of “works for me” situations. Dependency hell simply describes the complexity inherent in modern application’s tangled graph of external libraries and programs they need to function. Environmental hell is the name for the operating system portion of that same problem (i.e. what wrinkles, in particular which bash implementation,on which that quick script you wrote unknowingly relies).
Namespaces provide the solution in much the same way as virtual memory simplified writing code on a multi-tenant machine: by providing the illusion that an application suite has the computer all to itself. In other words,”via isolation”. When a process or process group is isolated via these new namespace features, we say they are “contained.” In this way, virtualization and containers are conceptually related, but containers isolate in a completely different way and conflating the two is just the first of a series of misconceptions that must be cleared up in order to understand how to use containers as securely as possible. Virtualization involves fully isolating programs to the point that one can use Linux, for example, while another uses BSD. Containers are not so isolated. Here are a few of the ways that “containers do not contain:”
- Containers all share the same kernel. If a contained application is hijacked with a privilege escalation vulnerability, all running containers *and* the host are compromised. Similarly, it isn’t possible for two containers to use different versions of the same kernel module.
- Several resources are *not* namespaced. Examples include normal ulimit systems still being needed to control resources such as filehandlers. The kernel keyring is another example of a resource that is not namespaced. Many beginning users of containers find it counter-intuitive that socket handlers can be exhausted or that kerberos credentials are shared between containers when they believe they have exclusive system access. A badly behaving process in one container could use up all the filehandles on a system and starve the other containers. Diagnosing the shared resource usage is not feasible from within
- By default, containers inherit many system-level kernel capabilities. While Docker has many useful options for restricting kernel capabilities, you need a deeper understanding of an application’s needs to run it inside containers than you would if running it in a VM. The containers and the application within them will be dependent on the capabilities of the kernel on which they reside.
- Containers are not “write once, run anywhere”. Since they use the host kernel, applications must be compatible with said kernel. Just because many applications don’t depend on particular kernel features doesn’t mean that no applications do.
For these and other reasons, Docker images should be designed and used with consideration for the host system on which they are running. . By only consuming images from trusted sources, you reduce the risk of deploying containerized applications that es. Docker images should be considered as powerful as RPMs and should only be installed from sources you trust. You wouldn’t expect your system to remain secured if you were to randomly install untrusted RPMs nor should you if you “docker pull” random Docker images.
In the future we will discuss the topic of untrusted images.
Morfy CMS v1.05 – Command Execution Vulnerability
Posted by Vulnerability Lab on Dec 17
Document Title:
===============
Morfy CMS v1.05 – Command Execution Vulnerability
References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1367
https://github.com/Awilum/monstra-cms/issues/351
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-9185
CVE-ID:
=======
CVE-2014-9185
Release Date:
=============
2014-12-10
Vulnerability Laboratory ID (VL-ID):
====================================
1367…
Bird Feeder v1.2.3 WP Plugin – CSRF & XSS Vulnerability
Posted by Vulnerability Lab on Dec 17
Document Title:
===============
Bird Feeder v1.2.3 WP Plugin – CSRF & XSS Vulnerability
References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1372
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-9334
CVE-ID:
=======
CVE-2014-9334
Release Date:
=============
2014-12-09
Vulnerability Laboratory ID (VL-ID):
====================================
1372
Common Vulnerability Scoring System:…
2014 Security Lessons: Making 2015 More Secure
A few days ago, I gave a webinar titled Make 2015 More Secure: Lessons from 2014, which was a follow-up to the 2014 Mid-Year Threat Report webinar from this summer.
The post 2014 Security Lessons: Making 2015 More Secure appeared first on We Live Security.
Four trends that will change mobile in 2015
In fact in the US mobile web traffic exceeded desktop web traffic for the first time. Mobile is fast becoming the most convenient and cost effective to way get online but what does the future hold for our smartphones?
Here are my predictions on how our mobile worlds will continue to evolve in 2015.
Apps will become the primary target for hackers

While the first generation of mobile threats was primarily using vectors and methods seen in the PC world, we are beginning to see new threats specifically designed to exploit mobile devices. The threats is not just malicious apps, but also regular apps that are vulnerable to attacks.
Until now, the centralized software distribution model seen with the AppStore and Google Play has helped protect our devices from malware. This concept came as a lesson we all learned from the PC, where software distribution is not controlled and so malware is common. Apps on official stores are less likely to be malicious, but it doesn’t mean they are not vulnerable to attacks.
Hackers love to find vulnerabilities. Almost every software program has vulnerabilities that are waiting to be discovered and mobile apps are not an exception. As official app stores make it difficult for hackers to directly upload malicious apps, they have instead begun hunting for vulnerable apps to attack.
Vulnerable Apps are not always removed from the App stores and as many have been left unmaintained by developers, creating an opportunity for hackers to exploit them.
New threats will emerge

As a result I expect to see a rise in the discovery of mobile app vulnerabilities during 2015. Here are a few examples:
- Voice activation – Voice activated software is a standard feature on smartphones and are also appearing in smart TVs and other Internet-connected devices. However many of the implementations are vulnerable to voice activation attacks. This is because it does not authenticate the source of the voice – it could be you speaking, or equally it could be a synthesized voice coming out of an app – yes, even a game can play a sound an send an email to your contacts on your behalf.
- Mobile browsers – For the average user, browsers on mobile are very difficult to operate. Small screens mean you see only a fraction of the URL, making it easy disguise a malicious URL. Drive-by infections, which are well known to PC users, will soon come to mobile users as well. Not surprising, mobile browsers are also vulnerable to JavaScript exploits that can be triggered by a hacker remotely. That could mean streaming video to or from a device, even if it is locked.
- Radio-based threats (Wi-Fi, Bluetooth, NFC) – mobile devices are constantly broadcasting over radio frequencies in order to connect and transfer data. Rough access points and over-the-air sniffers can capture transmitted data, reply with malicious content or even modify the values in the data over-the-air.
- Masque Attacks and malicious Profiles – as mobile users have less visibility on the files being downloaded on the device, like the running processes and settings, hackers will continue to use these limitations to mislead the user to download and install malicious files to their devices from outside the Appstore. However apps on app store are also vulnerable and I predict the number of malware detections from recognized app stores to increase in 2015.
Data will become more valuable and more threatened

Mobile devices are much more personal than our PCs ever could be. The data on them is much more intimate and is a much more rewarding target for hackers. In 2015, I expect data, especially that held on our mobile devices, to come under much greater scrutiny.
In particular, I foresee three threats to our data in the coming year:
- Physical tracking – criminals or law enforcement can use location data stored on your phone to identify important places (such as home or place of work), analyze behavior such as a daily route or absence from home.
- Data stealing – in mobile, everything is broadcast through the air, that means data is vulnerable to being intercepted as it travels. Credentials, financials, transactions or payments can all be captured and recorded by 3rd
- Commercial tracking – mainly done by retailers to better understand the behavior of their visitors. Think online analytics but for the physical world.
Payments will also go mobile

The public’s positive reception of Apple Pay heralded a new phase of consumer payment methodology. Although Apple is not the first to introduce mobile payment, their offering came at a good time and the implementation seems to be practical and secure.
As mobile payments are a new experience for consumers, I expect to see social engineering attacks where hackers will try to confuse and mislead in order to steal credentials and personal data. This is expected to be the first phase of attacks. Once consumers are more familiar with the technology, attacks on vulnerable apps and even on the payment services are expected to soar.
3 Tips for Geeks to Save Their Holidays
If you’re a geek, like most people, you’ll probably visit your family for Christmas.
Like most people, you probably want to enjoy nice holidays with relatives and friends.
Unlike most people, you’ll probably have to face (many) tricky infosec-related questions during this period. So here are a few tips for geeks on that topic.
Heartbleed
- you want to unlock your phone, so you concentrate, and think about your PIN
- someone near you shouts “tell me what you think, chicken”
- you answer honestly (because you’re vulnerable to this particular word, like Marty McFly)
- you just leaked your secret PIN

To be exact, Hearbleed is not about a PIN, it’s about encryption key, but they both grant access if you know them.
It’s not about a phone, it’s about a widely used security library called OpenSSL – and in particular the “Heartbeat” extension of OpenSSL (hence the name Heartbleed)
It’s a bit more complicated than just shouting ‘chicken’, but it’s not too complicated either ![]()
And like Heartbleed, it’s about ‘attacking’ at the right moment: you’ll just get whatever is in the target’s mind at the moment of the attack: “buy bread & milk”, or what’s on TV tonight… or an access PIN.
Goto fail
Here is a dialog between you and your grandma:
- You: “Grandma, you’ll guard that door. Follow exactly the instructions I’ll tell you now.”
- Grandma: “OK”
- Y: “The door should be closed”
- G: “OK”
- Y: “if it’s grandpa, leave the door open”
- G: “OK”
But then, your child comes behind you, and just repeats the last part of your sentence, imitating your voice.
- child: “leave the door open”
- G: “OK”
Now the door is permanently open. Just because a statement was accidentally repeated, out of its original context.
Consequences
This is as simple as that: since a conditional piece of code was executed in all cases because of a mistake, one of the security doors of Apple’s operating system was always open: if you knew which door to go to, you could bypass the whole security and enter without any problem.
Shellshock
Your grandpa speaks an old forgotten dialect.
You only know one sentence in this language.
Because you learned it so long ago that you can’t clearly remember, you just think it’s a common greeting.
But it actually means “do this now”.
And your grandpa – a fragile person due to his age – would actually blindly do anything you ask him.
So far, no one noticed because no one gave an order to your grandpa in his dialect.
Yet he was vulnerable all the time (or at least, for the past 25 years). He’d just do anything if asked the right way.
Sadly, it turned out that a lot of people would actually also do the same.
It wasn’t a mistake, just some old dialect that very few people consciously understood.
Conclusion
Of course, there were much more than 3 major events this year, but that might be enough to convince your audience, and save your holidays ![]()
I hope this will help to face your relatives & friends’ questions without boring them.
May you enjoy nice holidays – Merry Christmas / happy solstice!
The post 3 Tips for Geeks to Save Their Holidays appeared first on Avira Blog.