Secunia Research: Microsoft Windows Type 1 Font Processing Vulnerability
Monthly Archives: December 2016
Bugtraq: Adobe Animate <= v15.2.1.95 Memory Corruption Vulnerability
Adobe Animate <= v15.2.1.95 Memory Corruption Vulnerability
Bugtraq: Nagios Core < 4.2.2 Curl Command Injection leading to Remote Code Execution [CVE-2016-9565]
Nagios Core < 4.2.2 Curl Command Injection leading to Remote Code Execution [CVE-2016-9565]
One billion and one reasons to change your password

After another Yahoo’s data breach find out why you need to strengthen your security
Dear 2016, we want you to please be over already! PLEASE!
In a statement released by Yahoo yesterday they confirmed that there’s been another data breach. According to the press release the leaked information is associated with more than one billion Yahoo user accounts. The incident is different than the one reported few months ago. However, initial examinations suggest both attacks have been performed by the same hackers. There are a few things we recommend you to do right away to avoid becoming a victim of cybercrime. Don’t delay it!
When did this happen?
Yahoo confirmed the incident happened August 2013. Not to be mistaken with the data breach reported on September 22nd earlier this year.
What information was stolen?
No one really knows for sure, however the stolen information may have included personal information such as names, email addresses, telephone numbers, dates of birth, passwords and, in some cases, encrypted or unencrypted security questions and answers.
How is this affecting Yahoo?
In terms of branding and resonance, it’s the latest security blow against the former number one Internet giant. This kind of news won’t help user confidence in the company that has been heavily criticized by leading senators for taking two years to disclose the September 2014 breach. To make matters worse, this new one is from 2013. Yahoo was down more than 2.5 percent in after-hours trading on the Nasdaq in New York.
The company once valued at $125bn will not be sold for more than $5bn to Verizon. The price may go even lower. What make things really bad for Yahoo is that according to BBC, Yahoo knew about the hack but decided to keep quiet… not a smart move.
The good news
Even though your personal information has been circling the dark web for more than 2 years, you may not be affected at all. We are talking about 1 billion accounts – this is a lot of data to process. However, if you don’t change your passwords regularly or if you tend to keep using the same answers on security questions, you may be in danger.
Troublemakers might be able to use the information to get your bank details or commit identity fraud. It’s vital to be self-conscious and protect yourself. And if you do, you don’t have anything to worry about.
Even though Yahoo are working closely with law enforcement and they are doing their best to protect your data, changing your password regularly and installing an antivirus software is a must.
The post One billion and one reasons to change your password appeared first on Panda Security Mediacenter.
RHSA-2016:2947-1: Critical: flash-plugin security update
Red Hat Enterprise Linux: An update for flash-plugin is now available for Red Hat Enterprise Linux 6
Supplementary.
Red Hat Product Security has rated this update as having a security impact of
Critical. A Common Vulnerability Scoring System (CVSS) base score, which gives a
detailed severity rating, is available for each vulnerability from the CVE
link(s) in the References section.
CVE-2016-7867, CVE-2016-7868, CVE-2016-7869, CVE-2016-7870, CVE-2016-7871, CVE-2016-7872, CVE-2016-7873, CVE-2016-7874, CVE-2016-7875, CVE-2016-7876, CVE-2016-7877, CVE-2016-7878, CVE-2016-7879, CVE-2016-7880, CVE-2016-7881, CVE-2016-7890, CVE-2016-7892
RHEA-2016:2951-1: rhosp-director-images bug fix and enhancement update
Red Hat Enterprise Linux: Updated rhosp-director-images packages that fix several bugs and add
various enhancements are now available for Red Hat OpenStack Platform 10
(Newton) for Red Hat Enterprise Linux 7.
RHEA-2016:2948-1: Red Hat OpenStack Platform 10 enhancement update
Red Hat Enterprise Linux: New Red Hat OpenStack Platform 10.0 (Newton) packages that add features and fix
multiple bugs are now available for Red Hat Enterprise Linux 7.
RHBA-2016:2949-1: openvswitch bug fix update
Red Hat Enterprise Linux: Updated openvswitch packages are now available for Red Hat OpenStack Platform
for Red Hat Enterprise Linux 7.3
chromium-55.0.2883.87-1.el7.1
Update to Chromium 55.
Security fix for CVE-2016-9651, CVE-2016-5208, CVE-2016-5207, CVE-2016-5206, CVE-2016-5205, CVE-2016-5204, CVE-2016-5209, CVE-2016-5203, CVE-2016-5210, CVE-2016-5212, CVE-2016-5211, CVE-2016-5213, CVE-2016-5214, CVE-2016-5216, CVE-2016-5215, CVE-2016-5217, CVE-2016-5218, CVE-2016-5219, CVE-2016-5221, CVE-2016-5220, CVE-2016-5222, CVE-2016-9650, CVE-2016-5223, CVE-2016-5226, CVE-2016-5225, CVE-2016-5224, CVE-2016-9652, CVE-2016-5199, CVE-2016-5200, CVE-2016-5201, CVE-2016-5202
USN-3157-1: Apport vulnerabilities
Ubuntu Security Notice USN-3157-1
14th December, 2016
apport vulnerabilities
A security issue affects these releases of Ubuntu and its
derivatives:
- Ubuntu 16.10
- Ubuntu 16.04 LTS
- Ubuntu 14.04 LTS
- Ubuntu 12.04 LTS
Summary
Apport could be made to run programs as your login if it opened a
specially crafted file.
Software description
- apport
– automatically generate crash reports for debugging
Details
Donncha O Cearbhaill discovered that the crash file parser in Apport
improperly treated the CrashDB field as python code. An attacker could
use this to convince a user to open a maliciously crafted crash file
and execute arbitrary code with the privileges of that user. This issue
only affected Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-9949)
Donncha O Cearbhaill discovered that Apport did not properly sanitize the
Package and SourcePackage fields in crash files before processing package
specific hooks. An attacker could use this to convince a user to open a
maliciously crafted crash file and execute arbitrary code with the
privileges of that user. (CVE-2016-9950)
Donncha O Cearbhaill discovered that Apport would offer to restart an
application based on the contents of the RespawnCommand or ProcCmdline
fields in a crash file. An attacker could use this to convince a user to
open a maliciously crafted crash file and execute arbitrary code with the
privileges of that user. (CVE-2016-9951)
Update instructions
The problem can be corrected by updating your system to the following
package version:
- Ubuntu 16.10:
-
apport
2.20.3-0ubuntu8.2
-
python-apport
2.20.3-0ubuntu8.2
-
python3-apport
2.20.3-0ubuntu8.2
-
apport-kde
2.20.3-0ubuntu8.2
-
apport-gtk
2.20.3-0ubuntu8.2
- Ubuntu 16.04 LTS:
-
apport
2.20.1-0ubuntu2.4
-
python-apport
2.20.1-0ubuntu2.4
-
python3-apport
2.20.1-0ubuntu2.4
-
apport-kde
2.20.1-0ubuntu2.4
-
apport-gtk
2.20.1-0ubuntu2.4
- Ubuntu 14.04 LTS:
-
apport
2.14.1-0ubuntu3.23
-
python-apport
2.14.1-0ubuntu3.23
-
python3-apport
2.14.1-0ubuntu3.23
-
apport-kde
2.14.1-0ubuntu3.23
-
apport-gtk
2.14.1-0ubuntu3.23
- Ubuntu 12.04 LTS:
-
apport
2.0.1-0ubuntu17.15
-
python-apport
2.0.1-0ubuntu17.15
-
apport-kde
2.0.1-0ubuntu17.15
-
apport-gtk
2.0.1-0ubuntu17.15
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.