The Heartbleed Bug - OpenSSL

The Heartbleed Bug

The Heartbleed Bug is a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet. SSL/TLS provides communication security and privacy over the Internet for applications such as web, email, instant messaging (IM) and some virtual private networks (VPNs).

The Heartbleed bug allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users.

What leaks in practice?

We have tested some of our own services from attacker's perspective. We attacked ourselves from outside, without leaving a trace. Without using any privileged information or credentials we were able steal from ourselves the secret keys used for our X.509 certificates, user names and passwords, instant messages, emails and business critical documents and communication.

How to stop the leak?

As long as the vulnerable version of OpenSSL is in use it can be abused. Fixed OpenSSL has been released and now it has to be deployed. Operating system vendors and distribution, appliance vendors, independent software vendors have to adopt the fix and notify their users. Service providers and users have to install the fix as it becomes available for the operating systems, networked appliances and software they use.

---

Q&A

What is the CVE-2014-0160?

CVE-2014-0160 is the official reference to this bug. CVE (Common Vulnerabilities and Exposures) is the Standard for Information Security Vulnerability Names maintained by MITRE. Due to co-incident discovery a duplicate CVE, CVE-2014-0346, which was assigned to us, should not be used, since others independently went public with the CVE-2014-0160 identifier.

Why it is called the Heartbleed Bug?

Bug is in the OpenSSL's implementation of the TLS/DTLS (transport layer security protocols) heartbeat extension (RFC6520). When it is exploited it leads to the leak of memory contents from the server to the client and from the client to the server.

What makes the Heartbleed Bug unique?

Bugs in single software or library come and go and are fixed by new versions. However this bug has left large amount of private keys and other secrets exposed to the Internet. Considering the long exposure, ease of exploitation and attacks leaving no trace this exposure should be taken seriously.

Is this a design flaw in SSL/TLS protocol specification?

No. This is implementation problem, i.e. programming mistake in popular OpenSSL library that provides cryptographic services such as SSL/TLS to the applications and services.

What is being leaked?

Encryption is used to protect secrets that may harm your privacy or security if they leak. In order to coordinate recovery from this bug we have classified the compromised secrets to four categories: 1) primary key material, 2) secondary key material and 3) protected content and 4) collateral.

What is leaked primary key material and how to recover?

These are the crown jewels, the encryption keys themselves. Leaked secret keys allows the attacker to decrypt any past and future traffic to the protected services and to impersonate the service at will. Any protection given by the encryption and the signatures in the X.509 certificates can be bypassed. Recovery from this leak requires patching the vulnerability, revocation of the compromised keys and reissuing and redistributing new keys. Even doing all this will still leave any traffic intercepted by the attacker in the past still vulnerable to decryption. All this has to be done by the owners of the services.

What is leaked secondary key material and how to recover?

These are for example the user credentials (user names and passwords) used in the vulnerable services. Recovery from this leaks requires owners of the service first to restore trust to the service according to steps described above. After this users can start changing their passwords and possible encryption keys according to the instructions from the owners of the services that have been compromised. All session keys and session cookies should be invalided and considered compromised.

What is leaked protected content and how to recover?

This is the actual content handled by the vulnerable services. It may be personal or financial details, private communication such as emails or instant messages, documents or anything seen worth protecting by encryption. Only owners of the services will be able to estimate the likelihood what has been leaked and they should notify their users accordingly. Most important thing is to restore trust to the primary and secondary key material as described above. Only this enables safe use of the compromised services in the future.

What is leaked collateral and how to recover?

Leaked collateral are other details that have been exposed to the attacker in the leaked memory content. These may contain technical details such as memory addresses and security measures such as canaries used to protect against overflow attacks. These have only contemporary value and will lose their value to the attacker when OpenSSL has been upgraded to a fixed version.

Recovery sounds laborious, is there a short cut?

After seeing what we saw by "attacking" ourselves, with ease, we decided to take this very seriously. We have gone laboriously through patching our own critical services and are in progress of dealing with possible compromise of our primary and secondary key material. All this just in case we were not first ones to discover this and this could have been exploited in the wild already.

How revocation and reissuing of certificates works in practice?

If you are a service provider you have signed your certificates with a Certificate Authority (CA). You need to check your CA how compromised keys can be revoked and new certificate reissued for the new keys. Some CAs do this for free, some may take a fee.

Am I affected by the bug?

You are likely to be affected either directly or indirectly. OpenSSL is the most popular open source cryptographic library and TLS (transport layer security) implementation used to encrypt traffic on the Internet. Your popular social site, your company's site, commerce site, hobby site, site you install software from or even sites run by your government might be using vulnerable OpenSSL. Many of online services use TLS to both to identify themselves to you and to protect your privacy and transactions. You might have networked appliances with logins secured by this buggy implementation of the TLS. Furthermore you might have client side software on your computer that could expose the data from your computer if you connect to compromised services.

How widespread is this?

Most notable software using OpenSSL are the open source web servers like Apache and nginx. The combined market share of just those two out of the active sites on the Internet was over 66% according to Netcraft's April 2014 Web Server Survey. Furthermore OpenSSL is used to protect for example email servers (SMTP, POP and IMAP protocols), chat servers (XMPP protocol), virtual private networks (SSL VPNs), network appliances and wide variety of client side software. Fortunately many large consumer sites are saved by their conservative choice of SSL/TLS termination equipment and software. Ironically smaller and more progressive services or those who have upgraded to latest and best encryption will be affected most. Furthermore OpenSSL is very popular in client software and somewhat popular in networked appliances which have most inertia in getting updates.

What versions of the OpenSSL are affected?

Status of different versions:

·         OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable

·         OpenSSL 1.0.1g is NOT vulnerable

·         OpenSSL 1.0.0 branch is NOT vulnerable

·         OpenSSL 0.9.8 branch is NOT vulnerable

Bug was introduced to OpenSSL in December 2011 and has been out in the wild since OpenSSL release 1.0.1 on 14th of March 2012. OpenSSL 1.0.1g released on 7th of April 2014 fixes the bug.

How common are the vulnerable OpenSSL versions?

The vulnerable versions have been out there for over two years now and they have been rapidly adopted by modern operating systems. A major contributing factor has been that TLS versions 1.1 and 1.2 came available with the first vulnerable OpenSSL version (1.0.1) and security community has been pushing the TLS 1.2 due to earlier attacks against TLS (such as the BEAST).

How about operating systems?

Some operating system distributions that have shipped with potentially vulnerable OpenSSL version:

·         Debian Wheezy (stable), OpenSSL 1.0.1e-2+deb7u4

·         Ubuntu 12.04.4 LTS, OpenSSL 1.0.1-4ubuntu5.11

·         CentOS 6.5, OpenSSL 1.0.1e-15

·         Fedora 18, OpenSSL 1.0.1e-4

·         OpenBSD 5.3 (OpenSSL 1.0.1c 10 May 2012) and 5.4 (OpenSSL 1.0.1c 10 May 2012)

·         FreeBSD 10.0 - OpenSSL 1.0.1e 11 Feb 2013

·         NetBSD 5.0.2 (OpenSSL 1.0.1e)

·         OpenSUSE 12.2 (OpenSSL 1.0.1c)

Operating system distribution with versions that are not vulnerable:

·         Debian Squeeze (oldstable), OpenSSL 0.9.8o-4squeeze14

·         SUSE Linux Enterprise Server

·         FreeBSD 8.4 - OpenSSL 0.9.8y 5 Feb 2013

·         FreeBSD 9.2 - OpenSSL 0.9.8y 5 Feb 2013

·         FreeBSD 10.0p1 - OpenSSL 1.0.1g (At 8 Apr 18:27:46 2014 UTC)

·         FreeBSD Ports - OpenSSL 1.0.1g (At 7 Apr 21:46:40 2014 UTC)

How can OpenSSL be fixed?

Even though the actual code fix may appear trivial, OpenSSL team is the expert in fixing it properly so latest fixed version 1.0.1g or newer should be used. If this is not possible software developers can recompile OpenSSL with the handshake removed from the code by compile time option -DOPENSSL_NO_HEARTBEATS.

Should heartbeat be removed to aid in detection of vulnerable services?

Recovery from this bug could benefit if the new version of the OpenSSL would both fix the bug and disable heartbeat temporarily until some future version. It appears that majority if not almost all TLS implementations that respond to the heartbeat request today are vulnerable versions of OpenSSL. If only vulnerable versions of OpenSSL would continue to respond to the heartbeat for next few months then large scale coordinated response to reach owners of vulnerable services would become more feasible.

Can I detect if someone has exploited this against me?

Exploitation of this bug leaves no traces of anything abnormal happening to the logs.

Can IDS/IPS detect or block this attack?

Although the content of the heartbeat request is encrypted it has its own record type in the protocol. This should allow intrusion detection and prevention systems (IDS/IPS) to be trained to detect use of the heartbeat request. Due to encryption differentiating between legitimate use and attack can not be based on the content of the request, but the attack may be detected by comparing the size of the request against the size of the reply. This seems to imply that IDS/IPS can be programmed to detect the attack but not to block it unless heartbeat requests are blocked altogether.

Has this been abused in the wild?

We don't know. Security community should deploy TLS/DTLS honeypots that entrap attackers and to alert about exploitation attempts.

Can attacker access only 64k of the memory?

There is no total of 64 kilobytes limitation to the attack, that limit applies only to a single heartbeat. Attacker can either keep reconnecting or during an active TLS connection keep requesting arbitrary number of 64 kilobyte chunks of memory content until enough secrets are revealed.

Is this a MITM bug like Apple's goto fail bug was?

No this doesn't require a man in the middle attack (MITM). Attacker can directly contact the vulnerable service or attack any user connecting to a malicious service. However in addition to direct threat the theft of the key material allows man in the middle attackers to impersonate compromised services.

Does TLS client certificate authentication mitigate this?

No, heartbeat request can be sent and is replied to during the handshake phase of the protocol. This occurs prior to client certificate authentication.

Does OpenSSL's FIPS mode mitigate this?

No, OpenSSL Federal Information Processing Standard (FIPS) mode has no effect on the vulnerable heartbeat functionality.

Does Perfect Forward Secrecy (PFS) mitigate this?

Use of Perfect Forward Secrecy (PFS), which is unfortunately rare but powerful, should protect past communications from retrospective decryption. Please seehttps://twitter.com/ivanristic/status/453280081897467905 how leaked tickets may affect this.

Can heartbeat extension be disabled during the TLS handshake?

No, vulnerable heartbeat extension code is activated regardless of the results of the handshake phase negotiations. Only way to protect yourself is to upgrade to fixed version of OpenSSL or to recompile OpenSSL with the handshake removed from the code.

Who found the Heartbleed Bug?

This bug was independently discovered by a team of security engineers (Riku, Antti and Matti) atCodenomicon and Neel Mehta of Google Security, who first reported it to the OpenSSL team. Codenomicon team found heartbleed bug while improving the SafeGuard feature in Codenomicon's Defensics security testing tools and reported this bug to the NCSC-FI for vulnerability coordination and reporting to OpenSSL team.

What is the Defensics SafeGuard?

The SafeGuard feature of the Codenomicon's Defensics security testtools automatically tests the target system for weaknesses that compromise the integrity, privacy or safety. The SafeGuard is systematic solution to expose failed cryptographic certificate checks, privacy leaks or authentication bypass weaknesses that have exposed the Internet users to man in the middle attacks and eavesdropping. In addition to the Heartbleed bug the new Defensics TLS Safeguard feature can detect for instance the exploitable security flaw in widely used GnuTLS open source software implementing SSL/TLS functionality and the "goto fail;" bug in Apple's TLS/SSL implementation that was patched in February 2014.

Who coordinates response to this vulnerability?

NCSC-FI took up the task of reaching out to the authors of OpenSSL, software, operating system and appliance vendors, which were potentially affected. However, this vulnerability was found and details released independently by others before this work was completed. Vendors should be notifying their users and service providers. Internet service providers should be notifying their end users where and when potential action is required.

Is there a bright side to all this?

For those service providers who are affected this is a good opportunity to upgrade security strength of the secret keys used. A lot of software gets updates which otherwise would have not been urgent. Although this is painful for the security community, we can rest assured that infrastructure of the cyber criminals and their secrets have been exposed as well.

Where to find more information?

This Q&A was published as a follow-up to the OpenSSL advisory, since this vulnerability became public on 7th of April 2014. The OpenSSL project has made a statement athttps://www.openssl.org/news/secadv_20140407.txt. NCSC-FI published an advisory athttps://www.cert.fi/en/reports/2014/vulnerability788210.html. Individual vendors of operating system distributions, affected owners of Internet services, software packages and appliance vendors may issue their own advisories.

References

·         CVE-2014-0160

·         NCSC-FI case# 788210

·         OpenSSL Security Advisory (published 7th of April 2014, ~17:30 UTC)

·         CloudFlare: Staying ahead of OpenSSL vulnerabilities (published 7th of April 2014, ~18:00 UTC)

·         heartbleed.com (published 7th of April 2014, ~19:00 UTC)

·         Ubuntu / Security Notice USN-2165-1

·         FreshPorts / openssl 1.0.1_10

·         Tor Project / OpenSSL bug CVE-2014-0160

·         RedHat / RHSA-2014:0376-1

·         CentOS / CESA-2014:0376

·         Fedora / Status on CVE-2014-0160

·         CERT/CC (USA)

·         NCSC-FI (Finland)

·         CERT.at (Austria)

·         CIRCL (Luxembourg)

·         CERT-FR (France)

·         JPCERT/CC (Japan)

·         CERT-SE (Sweden)

·         NorCERT (Norway)

·         NCSC-NL (Netherlands)

·         CNCERT/CC (People's Republic of China)

·         Public Safety Canada

·         LITNET CERT (Lithuania)

·         MyCERT (Malaysia)

·         UNAM-CERT (Mexico)

·         SingCERT (Singapore)

·         Q-CERT (Qatar)

Source: http://heartbleed.com/

HttpLog- Unique HTTP request Logger,HTTP URL Logger, HTTP Request Logger Appliance with Full URL Log.

HTTP URL Logger, HTTP Request Logger Appliance with Full URL Log.

How to Fix Windows 8's Biggest Annoyances (and Make It More Like Windows 7)

How to Fix Windows 8's Biggest problems (and Make It More Like Windows 7)

Windows 8 has some awesome new features, but it also has its fair share of annoyances. Here's how to fix all of those problems, from bringing back missing features like the Start menu to fixing new problems like a dumbed-down Windows Explorer.

Bring Back the Start Menu

Look, we like Windows 8. It has some really cool stuff going for it, and most of the complaints surrounding it are misguided. However, there are a few annoyances that really need fixing. Instead of sticking with Windows 7 and missing out on Windows 8's improvements, we're going to show you how to get the best of both worlds.

Alternatively, you can use the free Classic Shell replacement, which is a tad more complicated but also more configurable than Start8. You have a lot more control over what your Start menu looks like, and can even tweak how the Search box works. When you install, you'll have the choice of installing just the Start menu or installing add-ons for Windows Explorer, Internet Explorer, and other programs too (more about this in a bit).The new Start screen isn't all that bad, but if you want the comfort of your old Start menu, it'sreally easy to bring back. Start8 is our favorite Start menu replacement, bringing a customizable start menu that fits in really well with Windows 8's new features and aesthetic. It's $5, but it's well worth the price and insanely easy to set up.

Get Rid of the Start Screen, Hot Corners, and More

If you really, really, really hate the tiled interface, you can get rid of it entirely with the aforementioned Classic Shell. Right-click on your Start menu and head into the settings. Under the "Windows 8 Settings" tab, you can check a box to skip the Start screen at login, as well as disable the hot corners if they trip you up. Start8 will also let you bypass the start screen, though it can't disable anything else.

If you're using Start8 instead of Classic Shell but want to disable the other "Metro" features, you can do so with a $5 program called RetroUI. It's simple: you can choose to bypass the Windows 8 Start screen after login, bypass the Start screen after locking your computer, or go all-out and get rid of everything: the Start screen, the Charms bar, and hot corners. Make sure you install Start8 first, or you'll have a lot of trouble opening programs and shutting down your computer since you won't have any of those functions available.

You can also disable the lock screen using Group Policy editor, if you so desire.

Customize the Ribbon-ified Windows Explorer

The new Windows Explorer has some cool features, but not everyone's a fan of the Ribbon interface. If that sounds like you, you have a few options for improving Explorer.

Classic Shell adds a new toolbar to Windows Explorer with small, simple buttons that you can customize to your heart's content. It isn't quite the same as having the old dropdown menus, but it's much simpler than the new Ribbon interface, and lets you add only the functions you'll actually use, which is nice. If you don't see it after installing Classic Shell, head to View > Options, click the Classic Explorer Bar to enable it, then click the seashell icon in the new toolbar to customize it.

Play DVDs for Free

However, if you prefer a more traditional file explorer with dropdown menus, you're better off with a full Explorer replacement likeXplorer₂. Not only will it give you all your advanced menus back, but you'll get tabs, two-pane browsing, tons of keyboard shortcuts, and a fantastic search feature. It won't be quite as pretty as the new Windows Explorer, but if you long for traditional menus rather than the new Ribbon, this is your best bet.

SEXPAND

Bad news, movie buffs: DVD playback is gone in Windows 8. Even if you download thecurrently-free Windows Media Center, it'll only allow you to play DVDs in Media Center—not in regular desktop programs like Windows Media Player.

If you want to play DVDs in Windows Media Player, it directs you to the Windows Store where you can buy an add-on for DVD support. Unless you really want to use WMP, don't waste your money—a program like VLC will play DVDs for free. Download it, install it, and forget about paying for DVD playback.

Bring Back the Confirmation Box When Deleting Files

In Windows 8, when you delete a file, it no longer asks you whether you're sure—it just sends the file right to the Recycle Bin. This was an option in Windows 7 as well, but it wasn't the default—and if you'd rather have that extra safety net, you can easily bring the confirmation dialog back. Just right-click on the Recycle Bin, choose Properties, and check the "Display Delete Confirmation Dialog" box.

Show the Desktop with a Hidden Button

Remember Aero Peek, the feature that let you hover over the edge of the taskbar to show your desktop? That's still around in Windows 8, but you have to enable it first. Right-click on the taskbar, choose Properties, and under the Taskbar tab check "Use Peek to Preview the Desktop." You won't see the button at the right edge of the taskbar like you did in Windows 7, but it's there—just hover your mouse over the area right of the clock and your windows will turn invisible again. You can also click this area to show the desktop instead of just peeking at it.

Replace Flip3D so You Can See Your Open Windows

Title image remixed from Yuri Arcurs (Shutterstock).Flip3D is also gone in Windows 8, but let's be honest: it wasn't that good to begin with. It was a nice piece of eye candy, but it wasn't exactly the most efficient way to see your open windows. There isn't a true replacement for Flip3D, but you can download a few programs that serve a similar purpose. Previously mentioned SmartFlip puts your windows in a wheel, letting you flip through them with whatever hotkey you want. Alternatively, you can download something like Switcher, which is more like OS X's Exposé, spreading your windows out into a grid when you press the desired hotkey. They won't bring back the eye candy of Flip3D, but they will serve the same purpose, and probably do it better.

Source: Lifehacker.com

Mikrotik Router - Step By Step Basic Configurations

Mikrotik Router - Step By Step Basic Configurations

This article explains how to configure Mikrotik device Router straight out of the box. It goes through the Winbox configuration utility and some of the basic setup procedures to turn your MikroTik device into a home or office wireless and wired router.

well In this tutorial we'll go through a step by step guide to make it as simple as possible to learn and implement these settings on your own routers.

These 4 Steps below are what we going to learn and setup for the beginning:

1. Downloading and running winbox
2. Setting an identity on the router
3. Setting an IP address on the router
4. Setting a password

STEP 1

Downloading and running winbox

Winbox is the graphical configuration utility designed for MikroTik RouterOS. It is a small application that can be downloaded from the MikroTik website athtttp://www.mikrotik.com Once you download winbox it can be run straight away, as no installation is required. It does however when running, setup a number of folders in your application data folder in order to save login data and plugins. This is transparent to the user but worthwhile to be aware, in order to diagnose problems and also understand the security implications of saving sensitive login information in the utility.

STEP 2

Setting an identity on the router

1. Download the latest Winbox Configuration Tool under the Tools and Utilities section at http://www.mikrotik.com/download.html and place it to youdesktop.
2. Double click on the Winbox icon on your desktop.
3. Click on System menu item then on the Identy sub menu as in the image below.
   
4. The Identity dialog will open as in image below. Remove the default "Mikrotik" value and replace it with something meaning full. Usually the location of the router combiened with its purpose acts as a suitable Identity for your router.
   

STEP 3
Setting an IP address on the router
To configure your Router IP Address
Click IP >> Addresses on the left menu in winbox as seen in image below.

This will open the Address list dialog window as seen below. Click on the red plus button to open the add IP address window.

When the New IP address dialog opens enter the address details select an interface to set the adress on and press apply and OK button.

For information on what IP settings to use please see a basic tutorial in IP Networking. But just to explain one or two points about this dialog...

It is best to delete an address entirely instead of editing it, as I found that it a cleaner way of editing an address as to modify network or broadcast options can sometimes not apply 100% properly.

You have an option of entering the network and broadcast address explicitly in the boxes provided or is you prefer you can use the short slash notation and press the apply button, this will populate the broadcast and network boxes with the correct settings.

STEP 4
Setting a password for Mikrotik

This tutorial demonistrates how to set the password of the current Mikrotik Winbox user.
Click on the menu item as shown below

System >> Password

This will open the password dialog box as shown below.

Enter the old or current password followed by the new password that you wish to use.

If this is your first time logging into the router or the router is on factory settings the Old password box should be just left blank. As the default username and password is admin and no password.

Note:
This is how you set the password of the current Winbox user. To change other users you must go to system >> users menu item open that dialog and set the password for that particular user. You must have adequate user privileges to perform this action.

setup PPPoE, NAT, DHCP server on Cisco Router

How to setup PPPoE, NAT,  DHCP server on Cisco Router 

Set up PPPoE, DHCP server, NAT in router cisco.
Figure:

Configuration file:

-------------------------------------------------------------------------------------------------
Current configuration : 1489 bytes
!
version 15.0
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Router
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
ip source-route
!
!
ip cef
!
!#########Create DHCP Server###########
ip dhcp pool InternalIP
   network 192.168.1.0 255.255.255.0
   dns-server 203.189.128.2 203.189.128.1
   default-router 192.168.1.1
!######################################
!        
!        
multilink bundle-name authenticated
!        
!        
!        
license udi pid CISCO2821 sn FGL151311SM
username cisco password 0 cisco
!        
!        
!        
!        
!        
!
!##############Enable PPPoE client on GigabitEthernet0/0##########        
interface GigabitEthernet0/0
 no ip address
 ip tcp adjust-mss 1452
 duplex auto
 speed auto
 pppoe enable group global
 pppoe-client dial-pool-number 1
 no cdp enable
!##################################################################
!        
interface GigabitEthernet0/1
 ip address 192.168.1.1 255.255.255.0
 ip nat inside
 ip nat enable
 ip virtual-reassembly
 ip tcp adjust-mss 1452
 duplex auto
 speed auto
!  
!###########setup PPPoE dialer 0 interface#################     
interface Dialer0
 description Connect to ONLINE
 ip address negotiated
 ip mtu 1454
 ip nat outside
 ip nat enable
 ip virtual-reassembly
 encapsulation ppp
 ip tcp adjust-mss 1452
 dialer pool 1
 dialer-group 1
 ppp authentication pap callin
 ppp pap sent-username Your_Username password 0 Your_Password
 no cdp enable
!###########################################################
!        
ip forward-protocol nd
!        
!        
no ip http server

###########Setup NAT########################
ip nat inside source list 99 interface Dialer0 overload
ip route 0.0.0.0 0.0.0.0 Dialer0
!        
access-list 99 permit 192.168.1.0 0.0.0.255

######################################
!        
!        
control-plane
!        
!        
line con 0
 login local
line aux 0
!##########Enable Telnet Access#########################
line vty 0 4
 privilege level 15
 password onlinecisco
 login
!#######################################################   
!        
scheduler allocate 20000 1000
end