SQL Injection vulnerability in extension Store Locator (locator)

Release Date: June 15, 2015

Component Type: Third party extension. This extension is not a part of the TYPO3 default installation.

Affected Versions:  version 3.3.0 and below

Vulnerability Type: SQL Injection

Severity: High

Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:C/I:C/A:P/E:F/RL:U/RC:C (What’s that?)

CVE: not assigned yet

Problem Description: Failing to properly sanitize user-supplied input, the extension is vulnerable to SQL-Injection.

Solution: An updated version 3.3.1 is available from the TYPO3 Extension Manager and at http://typo3.org/extensions/repository/download/locator/3.3.1/t3x/. Users of the extension are advised to update the extension as soon as possible.

Credits: Credits go to Franz G. Jahn who discovered and reported the issue.

 

General advice: Follow the recommendations that are given in the TYPO3 Security Guide. Please subscribe to the typo3-announce mailing list to receive future Security Bulletins via E-mail.

Arbitrary Code Execution in extension Frontend User Upload (feupload)

Release Date: June 15, 2015

Component Type: Third party extension. This extension is not a part of the TYPO3 default installation.

Affected Versions:  version 0.5.0 and below

Vulnerability Type: Arbitrary Code Execution

Severity: Critical

Suggested CVSS v2.0: AV:N/AC:L/Au:N/C:C/I:C/A:C/E:F/RL:U/RC:C (What’s that?)

CVE: not assigned yet

Problem Description: The extension feupload offers the possibility to upload files by using a frontend form. It was discovered that it is possible to upload all kind of files (e.g. PHP) which can be executed afterwards by knowing the filename and guessing the upload folder (which is fileadmin by default).

Solution: Versions of this extension that are known to be vulnerable will no longer be available for download from the TYPO3 Extension Repository. The extension author is no longer maintaining this extension. Please uninstall and delete the extension folder from your installation.

Credits: Credits go to Torben Hansen who discovered and reported the issue.

 

General advice: Follow the recommendations that are given in the TYPO3 Security Guide. Please subscribe to the typo3-announce mailing list to receive future Security Bulletins via E-mail.

SQL Injection vulnerability in extension Smoelenboek (ncgov_smoelenboek)

Release Date: June 15, 2015

Component Type: Third party extension. This extension is not a part of the TYPO3 default installation.

Affected Versions:  version 1.0.8 and below

Vulnerability Type: SQL Injection

Severity: High

Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:C/I:C/A:P/E:F/RL:U/RC:C (What’s that?)

CVE: not assigned yet

Problem Description: Failing to properly sanitize user-supplied input, the extension is vulnerable to SQL-Injection.

Solution: An updated version 1.0.9 is available from the TYPO3 Extension Manager and at http://typo3.org/extensions/repository/download/ncgov_smoelenboek/1.0.9/t3x/. Users of the extension are advised to update the extension as soon as possible.

Credits: Credits go to Wouter van Dongen who discovered and reported the issue.

 

General advice: Follow the recommendations that are given in the TYPO3 Security Guide. Please subscribe to the typo3-announce mailing list to receive future Security Bulletins via E-mail.

SQL Injection vulnerability in extension Developer Log (devlog)

Release Date: June 15, 2015

Component Type: Third party extension. This extension is not a part of the TYPO3 default installation.

Affected Versions: version 2.11.3 and below

Vulnerability Type: SQL Injection

Severity: High

Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:C/I:C/A:P/E:F/RL:U/RC:C (What’s that?)

CVE: not assigned yet

Problem Description: Failing to properly sanitize user-supplied input, the extension is vulnerable to SQL-Injection. Only editors with permissions to access the devlog backend module will be able to exploit this vulnerability.

Solution: An updated version 2.11.4 is available from the TYPO3 Extension Manager and at http://typo3.org/extensions/repository/download/devlog/2.11.4/t3x/. Users of the extension are advised to update the extension as soon as possible.

Credits: Credits go to Wouter van Dongen who discovered and reported the issue.

 

General advice: Follow the recommendations that are given in the TYPO3 Security Guide. Please subscribe to the typo3-announce mailing list to receive future Security Bulletins via E-mail.

Cross-Site Scripting in extension BE User Log (beko_beuserlog)

Release Date: June 15, 2015

Component Type: Third party extension. This extension is not a part of the TYPO3 default installation.

Affected Versions:  version 1.1.1 and below

Vulnerability Type: Cross-Site Scripting

Severity: Medium

Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:P/I:P/A:N/E:P/RL:U/RC:C (What’s that?)

Problem Description: The extension fails to properly escape user input in HTML context.

Solution: Versions of this extension that are known to be vulnerable will no longer be available for download from the TYPO3 Extension Repository. The extension author is no longer maintaining this extension. Please uninstall and delete the extension folder from your installation.

Credits: Credits go to Torben Hansen who discovered and reported the issue.

 

General advice: Follow the recommendations that are given in the TYPO3 Security Guide. Please subscribe to the typo3-announce mailing list to receive future Security Bulletins via E-mail.

SQL Injection vulnerability in extension FAQ – Frequently Asked Questions (js_faq)

Release Date: June 15, 2015

Component Type: Third party extension. This extension is not a part of the TYPO3 default installation.

Affected Versions: version 1.2.0 and below

Vulnerability Type: SQL Injection

Severity: High

Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:C/I:C/A:P/E:F/RL:U/RC:C (What’s that?)

CVE: not assigned yet

Problem Description: Failing to properly sanitize user-supplied input, the extension is vulnerable to SQL-Injection.

Solution: An updated version 1.2.1 is available from the TYPO3 Extension Manager and at http://typo3.org/extensions/repository/download/js_faq/1.2.1/t3x/. Users of the extension are advised to update the extension as soon as possible.

Credits: Credits go to Torben Hansen who discovered and reported the issue.

 

General advice: Follow the recommendations that are given in the TYPO3 Security Guide. Please subscribe to the typo3-announce mailing list to receive future Security Bulletins via E-mail.

SQL Injection vulnerability in extension wt_directory (wt_directory)

Release Date: June 15, 2015

Component Type: Third party extension. This extension is not a part of the TYPO3 default installation.

Affected Versions:  version 1.4.1 and below

Vulnerability Type: SQL Injection

Severity: High

Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:C/I:C/A:P/F:P/RL:O/RC:C (What’s that?)

CVE: not assigned yet

Problem Description: Failing to properly sanitize user-supplied input, the extension is vulnerable to SQL-Injection.

Solution: An updated version 1.4.2 is available from the TYPO3 Extension Manager and at http://typo3.org/extensions/repository/download/wt_directory/1.4.2/t3x/. Users of the extension are advised to update the extension as soon as possible. Please note: The extension author is no longer maintaining this extension. Therefore it is marked as obsolete and should not longer be used.

Credits: Credits go to Marc Bastian Heinrichs who discovered and reported the issue.

 

General advice: Follow the recommendations that are given in the TYPO3 Security Guide. Please subscribe to the typo3-announce mailing list to receive future Security Bulletins via E-mail.

OPM: Are Personnel Records of All Fed Workers Exposed?

Two weeks ago OPM, the US Office of Personnel Management got hacked and the information of 4 million federal government workers was exposed. This is of course, horrible. But it’s not all: On Friday we learned that the issue at hand was huge and much bigger than everyone believed at first.

As can be read in a letter to OPM Director Karen Archuletta, David Cox, the president of the  American Federation of Government Employees, believes that “based on the sketchy information OPM has provided, the Central Personnel Data Files was the targeted database, and the hackers are now in possession of all personnel data for every federal employee, every federal retiree, and up to one million former federal employees.”

Cox goes on and says that the thinks the hackers have the Social Security number, military records and even veterans status’ information of every affected person. Addresses, birth dates, job and pay histories, health and life insurances and pension information, age, gender, and almost everything else you’d never want anyone else to know are included on his list as well.

Sounds bad? It’s not all. The letter states: “Worst, we believe that Social Security numbers were not encrypted, a cybersecurity failure that is absolutely indefensible and outrageous.”

I bet they now wish that “only” 4 million records got stolen … :(

The post OPM: Are Personnel Records of All Fed Workers Exposed? appeared first on Avira Blog.

Facebook shields your messages: even the notification email will be encrypted

key closing door

If we were not aware of the eyes that watch over us on the Internet, Edward Snowden confirmed two years ago that American authorities monitor all our conversations. The former contractor at the NSA revealed that agents of the intelligence services roam freely in our private inboxes.

Then, many technology companies reassured their users and took some actions, but there are still things to do in order to ensure the total security of the conversations. One of the companies that seems ready to settle any suspicion about a possible intrusion is Facebook. According to the latest undertaken actions, everything points to the fact Mark Zuckerberg’s team wants to make it even more difficult for those who intend to snoop around others people’s conversations.

All the users’ connections with Facebook’s servers, including sent and received messages, are already transmitted via secure HTTPS protocol. As if this isn’t enough, the social network has also launched a Tor network service for the reassurance of their most demanding users with respect to privacy.

However, besides the connections that users establish through the service itself, there are other communications which are made via Facebook indirectly, via email. They are the notifications that you receive, for example, when a friend sends you a direct message (unless you have disabled this service).

Since the safety of these messages was not so assured, Facebook has announced that, from now on, all users – if they so decide – may receive them protected by the popular encryption Pretty Good Privacy (PGP). PGP hides the emails from potential intruders with a code system based on a public one (which the sender must have) and a private one (which only the receiver has).

mark zuckerberg

The Setup process is simple:

  • Access your profile
  • Click on the ‘Information‘ section
  • Go to ‘Basic and contact information’. From now on you can also introduce here your PGP public code (if you don’t know what it is or how to get it, the best thing you can do is to read a tutorial), which will be displayed in your profile, available to anyone who wants to send you an encrypted email.

Below the panel you will see a box on which you will have to click if you want all the notifications that Facebook sends you, from now on, also to incorporate this security layer.

like facebook

So whenever the encryption is used, it is very important to remember the code you established to protect your email with PGP. If one day you forget it, you won’t be able to read the notifications from Facebook, and you could lose your account on the social network.

How could you reach this far? Imagine that you had to use, for any reason, the typical Facebook password recovery email: the email would arrive encrypted, and you would only be able to read it and restore the ‘password’ if you can decode it. If you have forgotten our PGP private code in addition to your Facebook password, then you have a problem.

But don’t worry: it gets worse for the cybercriminal who tries to assault your account using the password recovery procedure. This trick will never be useful again. If he doesn’t have the PGP private code which decodes the emails that you receive, he would not be able to restore the password, even if he has access to the Facebook’s mail, because it will be encrypted.

It is a great security measure, without a doubt, which Facebook has just implemented. Now we will just have to wait to see if Zuckerberg’s network is an exception or other social networks decide to make a commitment to the safety of their users.

The post Facebook shields your messages: even the notification email will be encrypted appeared first on MediaCenter Panda Security.