tracker issue : CF-3746561

select a category, or use search below
(searches all categories and all time range)
Title:

Running CF10 websockets HelloWorld works but calls the errorhandler JS function in CF11

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/NotABug

Reporter/Name(from Bugbase): Mike Collins / Mike Collins (Mike Collins)

Created: 04/21/2014

Components: Web Socket

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: PublicBeta /

Priority/Frequency: Critical / Most users will encounter

Locale/System: ALL / Win 2008 Server R2

Vote Count: 0

When I run the code from http://www.adobe.com/devnet/coldfusion/articles/html5-websockets-coldfusion-pt2.html  (V6 from the zip file) it works in CF10 but throws an error when I click the  Agree button in CF11.  The app functions fine it just throws an error on the I Agree call.

I am not sure what could be different from 10 to 11, but 10 did not call the errorhandler JS function.  

This might be some incompatible JS code, or something different in the core cfwebsocket js libraries.  

If it's old sample code that is fine, but it seems more like something else.

Once again the app works so it seems like the errorhandler is getting called improperly.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3746561

External Customer Info:
External Company:  
External Customer Name: mcollins323
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

Hi, We have fixed a web socket vulnerability which prevents the ability to invoke non-remote methods on the CFC using Websockets. Adobe ColdFusion 10 before Update 11 allows remote attackers to call ColdFusion Components (CFC) public methods via WebSockets. getallclints.cfc and invoke.cfc both have public methods defined in it, which we are accessing remotely using WebSockets. Change the method access specifier from public to remote to make it work. You can change the logging level from warning to debug in the neo-websocket.xml file to debug this issue.
Comment by Nimit S.
12601 | April 22, 2014 02:04:38 AM GMT