Welcome!

Microservices Expo Authors: Stackify Blog, Elizabeth White, Dalibor Siroky, Pat Romanski, Liz McMillan

Related Topics: Cloud Security, Mobile IoT, Microservices Expo, ColdFusion, IBM Cloud, Weblogic, Linux Containers, Open Source Cloud, Containers Expo Blog, Machine Learning , Agile Computing, Release Management , Recurring Revenue, Log Management, @CloudExpo, Apache, Government Cloud

Cloud Security: Interview

Bulletproofing the WebSocket Wire Protocol

There's been a flurry of discussion this week among Internet & Web standards experts about the WebSocket communications protocol

Web Security Journal: There's been a flurry of discussion this week among Internet and Web standards heavy-hitters around WebSocket, the new communications protocol supported in Chrome 4 and Safari 5. What was the main issue? Is there some kind of fundamental security vulnerability with the WebSocket (WS) protocol?

John Fallows: When surfing the Web, our browsers may communicate with Web servers via HTTP proxies that deliver many benefits, such as providing previously cached Web content more efficiently than repeatedly contacting the target server. These proxies may be either explicitly configured at the browser or they may form part of the general network topology to intercept the communication path implicitly. Securely encrypted Web communication cannot be intercepted by such proxies.

Members of the Hypertext Bidirectional (HyBi) IETF Working Group recently completed a study to test the vulnerabilities of these implicit, intercepting HTTP proxies. The study found that the raw socket capabilities of Flash and Java could be used to mount an attack on these intercepting HTTP proxies, such that an attacker might be able to influence the contents of the cache and change the behavior of specific sites for users accessing those sites through the same intercepting HTTP proxy.

The results showed that of the 47,338 intercepting HTTP proxies tested with the unencrypted WebSocket handshake alone, 0.37% and 0.017% were found vulnerable for the two specific attacks described in the study.

Web Security Journal: If the flaw lies not in WebSockets, but in some particular type of proxies, why are commentators inclining towards discussing WebSockets and only WebSockets?

Fallows: If all intercepting HTTP proxies correctly implemented the HTTP standard, then the 101 Switching Protocols response used by WebSocket handshake would be both sufficient and elegant.

Even though these intercepting HTTP proxies vulnerabilities have been enabled by Flash and Java for a long time, they were reported in the study as part of the IETF working group design process for the WebSocket wire protocol, therefore commentators have been inclined to comment specifically about the WebSockets portion of this result.

In the short term, browser providers have elected to temporarily withdraw the JavaScript WebSocket API from deployed browser implementations until they and others in the IETF working group reach agreement on how to bulletproof the WebSocket wire protocol to handle even buggy implementations of intercepting HTTP proxies. There are already proposals in place so I anticipate a timely resolution early next year.

Web Security Journal: The tests that spurred Mozilla and Opera to disable WebSockets as the default were done with Java and Flash clients. That means presumably that this issue has been around long before WebSockets? Why hasn't it been caught and dealt with before?

Fallows: The WebSocket wire protocol design effort has brought together a huge community of experts to deliver this functionality such that it can be deployed on a global scale, which necessitates such experiments to validate the standards compliance of deployed HTTP proxy infrastructure.

It will be interesting to see how Adobe and Oracle respond to address the vulnerabilities enabled by raw socket access in Flash and Java. Perhaps this will encourage them to adopt WebSockets as a native part of their platform, and have a more restrictive policy on raw socket access for Web deployments of their plug-in technologies.

Web Security Journal: What's the exact current status, then? The protocol is being standardized by the IETF as we speak, but what about the WebSocket API overall? What's its status vis-a-vis the W3C?

Fallows: The W3C JavaScript WebSocket API remains unchanged in its definition. However, browser providers await resolution of the WebSocket wire protocol at the IETF before deploying an implementation.

Web Security Journal: So is it accurate to describe WebSockets - still - as an early stage specification at the moment?

Fallows: The WebSocket wire protocol is currently in the IETF Internet Draft stage, and there is no shortage of support or dedication in the Hypertext Bidirectional Working Group to reach completion in a timely manner.

Web Security Journal: You mentioned earlier that there's no real barrier to improving the WebSocket protocol the moment it is bulletproofed to withstand broken infrastructure, since such an improvement can simply be included in the latest update of whatever browser a user is using. But the creator of JavaScript, Brendan Eich, has warned that we might end up with what he calls "version skew" because users won't necessarily switch browsers just to get the latest version of WS. He asks, rhetorically: "Are we going to synchronize Firefox's release cycle with Chrome's? Is Opera? Is Safari?" Isn't that a valid concern?

Fallows: Web browsers have always innovated beyond the standards, in part to differentiate themselves and in part to drive the standards forward with the benefit of real-world experience. WebSocket is a good example of that, having evolved beyond both Ajax and Comet, as well as raw socket communication provided by plug-ins. If we are careful to provide a stable and extensible WebSocket base, as was achieved with HTTP, then I would fully expect to see browsers implementing custom enhancements to that base, and it will be the responsibility of WebSocket gateway providers to support for those enhancements.

Web Security Journal: Mozilla, despite disabling it as the default in Firefox 4, says it is "excited" by WebSockets. Why is such a major browser player "excited" - what is it about WebSockets that gets a major Internet force like the Mozilla Foundation to be so upbeat about its potential?

Fallows: WebSockets, and HTML5 in general, represent a leap forward for the Web application platform and it is certainly an "exciting" time for all of us using the Web today. For decades we have seen the evolution of Web applications with gradually increasing interactivity getting closer and closer to their desktop installed counterparts. WebSockets allows us to add the final piece of that puzzle, providing desktop class TCP network connectivity while traversing the HTTP-constrained infrastructure of the Web. A new breed of applications can now be built using WebSocket with a fraction of the server-side infrastructure costs, optimized network bandwidth utilization and more immediate delivery of time-sensitive information.

Web Security Journal: And where does the WebSocket protocol sit in terms of HTML5 specification?

The WebSocket wire protocol is governed by the IETF who manage many of the world's protocols like HTTP, FTP, SMTP, and others.

The W3C standards body maintains the both HTML5 specification and the WebSocket API specification which defines how JavaScript applications can leverage WebSocket functionality.

Browser providers depend on both standards to fully deliver WebSocket functionality.

Web Security Journal: Adam Barth, whose paper on a possible exploit of transparent proxies sparked this latest discussion, has also described a handshake for the WebSocket protocol that resists cross-protocol attacks. Is that the direction the IETF will go do you think?

Fallows: Ultimately there are a few ways to proceed that balance HTTP compatibility with strategies to overcome non-compliant HTTP proxies. Given that the same study demonstrated no successful attacks on Adam's proposed enhancement to the WebSocket handshake, it seems to be a very strong candidate as we move forward.

Web Security Journal: Can't a WebSocket connection simply be encrypted? Wouldn't that render this whole issue moot - or is that too simplistic?

Fallows: The attacks identified by Adam Barth's paper would not be possible using an encrypted WebSocket connection because the HTTP proxy would not be able to see the encrypted wire traffic and could therefore not be confused into triggering the buggy behavior. If the browser providers restricted encrypted-only access to WebSockets then this issue could be avoided.

Web Security Journal: So from a Kaazing perspective, then, is it your intention to propagate the world with WebSockets and then go to sleep with the feeling of a job well done, or is the propagation of WS gateways the means to some other kind of business goal?

Fallows: At Kaazing, we believe that WebSockets is the beginning of a new future for Web applications as we move from the disconnected world of yesterday to the always connected, always up-to-date world we live in today. We understand that while WebSockets provide the foundation of that new beginning, the majority of the new capabilities lie in how you use WebSocket to support higher-level protocols that make it straightforward to solve technical challenges that would have taken significantly more effort to achieve otherwise.

Our goals are to help to world transition to this new standard easily and efficiently, and continue to deliver solutions that eliminate the unnecessary architectural complexity found in many Web applications today.

Web Security Journal: And is anybody yet finding that they can make more money, or spend less, because of Kaazing's offerings? Are there real-world implementations at all?

Fallows: We have customers in the Financial Services, Sports Betting, and Online Auctions markets that have used our technology to reduce infrastructure costs, reduce time-to-market, improve end-user experience and drive their revenues more efficiently.

Web Security Journal: What, in your view, is the best way of channeling developers' interest in experimenting with what a WebSocket gateway can do for their architecture? How can someone who is not yet au fait with the technbology most easily play catch-up?

Fallows: The WebSocket.org site is dedicated to explaining the various aspects of WebSocket technology and would be a useful starting point for those wishing to read up. It contains links to the relevant WebSocket API and wire protocol specifications, including a discussion of the many benefits of WebSockets.

A developer download of Kaazing WebSocket Gateway is also freely available from kaazing.com. This delivers emulation of the standard WebSocket API for all browsers. So in the interim until browser providers re-enable WebSockets, developers can still experiment with the same WebSocket APIs in both current and older browsers that will prepare them for the future of Web communication.

More Stories By Security News Desk

SYS-CON's Security News desk trawls the world of security for news of software, hardware, products, and services that seems likely to be of interest to infosec professionals and summarizes them for easy assimilation by busy IT managers and staff.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
It has never been a better time to be a developer! Thanks to cloud computing, deploying our applications is much easier than it used to be. How we deploy our apps continues to evolve thanks to cloud hosting, Platform-as-a-Service (PaaS), and now Function-as-a-Service. FaaS is the concept of serverless computing via serverless architectures. Software developers can leverage this to deploy an individual "function", action, or piece of business logic. They are expected to start within milliseconds...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory? In her Day 2 Keynote at @DevOpsSummit at 21st Cloud Expo, Aruna Ravichandran, VP, DevOps Solutions Marketing, CA Technologies, was jo...
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and co...
The cloud era has reached the stage where it is no longer a question of whether a company should migrate, but when. Enterprises have embraced the outsourcing of where their various applications are stored and who manages them, saving significant investment along the way. Plus, the cloud has become a defining competitive edge. Companies that fail to successfully adapt risk failure. The media, of course, continues to extol the virtues of the cloud, including how easy it is to get there. Migrating...
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
From manual human effort the world is slowly paving its way to a new space where most process are getting replaced with tools and systems to improve efficiency and bring down operational costs. Automation is the next big thing and low code platforms are fueling it in a significant way. The Automation era is here. We are in the fast pace of replacing manual human efforts with machines and processes. In the world of Information Technology too, we are linking disparate systems, softwares and tool...
DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies? We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measure...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
"As we've gone out into the public cloud we've seen that over time we may have lost a few things - we've lost control, we've given up cost to a certain extent, and then security, flexibility," explained Steve Conner, VP of Sales at Cloudistics,in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
These days, APIs have become an integral part of the digital transformation journey for all enterprises. Every digital innovation story is connected to APIs . But have you ever pondered over to know what are the source of these APIs? Let me explain - APIs sources can be varied, internal or external, solving different purposes, but mostly categorized into the following two categories. Data lakes is a term used to represent disconnected but relevant data that are used by various business units wit...
With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
"Cloud4U builds software services that help people build DevOps platforms for cloud-based software and using our platform people can draw a picture of the system, network, software," explained Kihyeon Kim, CEO and Head of R&D at Cloud4U, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...