Multiple IBM Products CVE-2016-0325 Remote Command Injection Vulnerability
IBM Security Privileged Identity Manager CVE-2016-0353 Information Disclosure Vulnerability
Multiple IBM Products CVE-2016-2864 Cross Site Scripting Vulnerability
Multiple IBM Rational Products CVE-2016-0372 Remote Information Disclosure Vulnerability
Multiple Huawei Secospace Products CVE-2016-8802 Buffer Overflow Vulnerability

(credit: Aurich Lawson)

A low-tech but cunning malware program is worrying security researchers after it started spreading rapidly in the past week through a new attack vector: by forcibly exploiting vulnerabilities in Facebook and LinkedIn.

According to the Israeli security firm Check Point, security flaws in the two social networks allow a maliciously coded image file to download itself to a user's computer. Users who notice the download, and who then access the file, cause malicious code to install "Locky" ransomware onto their computers.

Locky has been around since early this year, and works by encrypting victims' files and demands a payment of around half a bitcoin (currently £294; $365) for the key. Previously, it had relied on a malicious macro in Word documents and spam e-mails, but Check Point says that in the past week there has been a "massive spread of the Locky ransomware via social media, particularly in its Facebook-based campaign."

Read 6 remaining paragraphs | Comments

Multiple Huawei Products CVE-2016-8768 Local Privilege Escalation
phpMyAdmin PMASA-2016-71 Security Bypass Vulnerability
Linux Kernel CVE-2016-8650 Null Pointer Deference Local Denial of Service Vulnerability
phpMyAdmin PMASA-2016-69 Multiple SQL Injection Vulnerabilities

Enlarge / Block G is one of the largest wartime structures at the site. (credit: Qufaro)

Bletchley Park—the home of codebreakers whose pioneering work helped Britain and its allies win the Second World—could be the site for a College of National Security, with plans for it to open in 2018.

The new sixth-form boarding school will, we're told, be run by a private non-profit consortium of tech firms, venture capitalists, and entrepreneurs, with rumoured input from GCHQ. It will enrol 500 teenagers (aged 16 to 19) who will be taught cybersecurity skills—which could, it's hoped, go some way to addressing the shortfall in UK talent.

The outfit behind the college, which would apparently be free for its pupils to attend, says at least part of the syllabus would be set by infosec experts focusing mostly on cybersecurity (roughly 40 percent of the curriculum), with additional modules on maths, computer science, economics, and physics also taught over a three-year period of study. Applicants won't be selected on the basis of specific academic qualifications, so much as through aptitude tests set by the college, or even on the basis of previously demonstrated skills, such as self-taught coding.

Read 8 remaining paragraphs | Comments

CakePHP Multiple Security Bypass Vulnerabilities
Multiple Cisco Products CVE-2016-1409 Remote Denial of Service Vulnerability
Multiple Huawei Products Local Multiple Security Vulnerabilities
PHP libicu 'locale_get_display_name()' Stack Buffer Overflow Vulnerability
phpMyAdmin PMASA-2016-59 Remote Information Disclosure Vulnerability
phpMyAdmin PMASA-2016-60 Remote Multiple Security Bypass Vulnerabilities
Moxa SoftCMS Multiple Security Vulnerabilities

Free software (open source or not) is interesting for many reasons. It can be adapted to your own needs, it can be easily integrated within complex architectures but the most important remains, of course, the price. Even if they are many hidden costs related to free software. In case of issues, a lot of time may be spent in searching for a solution or diving into the source code (and everybody knows that time is money!).

Today, more and more organisationsare not afraid anymore to deployfree software in their infrastructure butare those solutions really secure? A customer came to me with an interesting question about performing asecurity audit of free software. The idea is to validate the software before deploying it in his (very sensitive) infrastructure. This could be seen as a kind of quality insurance.

The idea is not to perform a deep source code review or to pentest the tool but more to establisha checklist of key points. I already compiled a rough list of questions that Id like to share with you:

  • What is the programming language used?
    Not all languages have the same security maturity. Some applications rely on functions that may become obsolete and prevent regular updates (PHP is a good example). Is a specific version of the language required? (eg. Python 2 VS. Python 3). Also writing secure code in C or Perl isnt as easy as other languages.
  • Architecture and security framework?
    Can the application be deployed in a virtual environment, is there a Docker container available? Are they other software components required (like a database server, a Redis server, ...). How easy may the application be deployed in high-availability? Does it work properly behind a reverse-proxy (in case of a web application)? Is it integrated or another software layer is required?
  • Regular updates?
    Pieces of software have bugs and security issues. How are patches released and how often?How reactive are the developers? If there is a bug tracking system, check the average time required to fix an issue. Some projects are very impressive and roll out fixes within hours of being notified while others arent as impressive. It must meet the same patching requirements as all other software.
  • Roadmap for the coming months?
    Is there a roadmap in place with new features? Can users propose and submit new features?
  • How big is the community around the project?
    Check out forums, mailing lists, issues reported on Are they regular commits? Are developers easily reachable? How many messages are posted on public resources?
  • How big is the current users base?
    If the existing users base is large, there are chances that bugs will be found quickly and new features suggested. Do current users look happy while using the application?
  • The documentation and quality of documentation within the code?
    A good documentation of the code means that it is maintainable. Documentation is mandatory to operate the application and to help to resolve issues.
  • Are external pieces of code (like libraries) used?
    Most applications rely on external libraries (think about OpenSSL). These pieces of code must follow the same process.
  • Data management?
    How safe is data used / generated by the application? Think about data in use,at rest and in move. Arebackup and restore procedures available?
  • Is there enough granularity in the configuration?
    How the application supports complex configuration? How deep can it be customized? Does it implement AAA (Authentication, Authorization Accounting), RBAC (Role Based Access Control).
  • Extendability of the application?
    Is the application modular and can be expanded with modules or plugins? If you consider a popular application likeWordpress, the core is fairly well maintained, but plugins introduce most vulnerabilities, and may or may not get maintained very well, so you might suggest that 3rd party modules added to a free package be treated as separate pieces of software.
  • Age and maturity of the project?
    If a new software has been released yesterday, it will be more difficult to review it.
  • What is the license used to distribute the software?
    The license must be reviewed to ensure there are no restrictions on its intended use. A lot of free software is not free for corporate use. If you have plans to adapt the software to your own needs, how to not break the existing license?
  • Integration with other tools?
    Is is easy to integrate the applications with authentication mechanisms (LDAP, RADIUS)? Can logs be easily exported? (Syslog, CEF)
  • Are they CVE related to the software?
    How many CVEs released in the last x months? What is the severity ofCVEs? Repeated issues inCVEs(did they just fix that one instance or look at the rest of the code base for similar issues and fix them as well). If a piece of software released recently has noCVEsassociated with it, it doesnt indicate that its secure. More CVEs could mean that code quality is not good or that more people areanalyzing the code and finding holes.On the other side, a lack of CVEs doesnt necessarily make a particular piece of code more secure. I suggest keeping track of CVEs issued and how quickly patches are released to correct CVEs and basing your decision on that.
  • Used in commercial solutions?
    If commercial companies embedded the project in their products, these companies have huge teams of developers that could ensure that security issues will be fixed.
  • Commercial support?
    Can a freelance be hired to help in the integration or the debug of issues?
If youve resources, a quick source code analysis for key areas like access control, authentication, encryption, SQL handling could be helpful. If the application relies on binaries, why not execute it through a sandbox like Cuckoo to detect potential issues like a backdoor.

As a final remark, there is no specific reason not to perform the same for commercial products. Mostcommercial products either use or depend on open source libraries/software.Alsokeep in mind that a commercial product doesnt mean a secure one.

Do you have other controls that could be added to the list? Feel free to share your comments!

Xavier Mertens (@xme)
ISC Handler - Freelance Security Consultant

(c) SANS Internet Storm Center. Creative Commons Attribution-Noncommercial 3.0 United States License.
Xen CVE-2016-9386 Privilege Escalation Vulnerability
Xen CVE-2016-9382 Privilege Escalation Vulnerability
Xen CVE-2016-9385 Denial of Service Vulnerability
IBM FileNet Workplace CVE-2016-5981 Unspecified Cross Site Scripting Vulnerability
IBM Jazz Foundation CVE-2016-2947 Information Disclosure Vulnerability
IBM Tealeaf Customer Experience Server Side Request Forgery Security Bypass Vulnerability
[SECURITY] [DSA 3724-1] gst-plugins-good0.10 security update
Call for Participation - 5th International Conference on Cyber Security, Cyber Welfare and Digital Forensic
Call for Participation - 5th International Conference on Cyber Security, Cyber Welfare and Digital Forensic
WorldCIST'17 - Submission deadline: November 27
[SECURITY] [DSA 3723-1] gst-plugins-good1.0 security update
Internet Storm Center Infocon Status