Openfire

Client session will be terminate when receiving invalid surrogate characters

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Blocker Blocker
  • Resolution: Duplicate
  • Affects Version/s: 3.6.4
  • Fix Version/s: 3.7.0 beta
  • Component/s: Connection Manager, Core
  • Labels:
    None
  • Acceptance Test - Add?:
    No

Description

Client session will be terminate when receiving invalid surrogate characters

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. OF-391 Security-related issue reported by Mark Doliner at August 17, 2010.

  • Blocker - Blocks development and/or testing work, production could not run.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
is related to

Bug - A problem which impairs or prevents the functions of the product. JM-1421 Server should disconnect clients sending invalid XML

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ilan Rabinovitch added a comment -

Would it be possible to confirm if this is related to the issues mentioned in the Pidgin and AdiumX bug trackers? Both tickets reference, but indicate they were unable to confirm if this was the solution. I know that as of openfire 3.5.2 the invalid characters still terminate client sessions for Pidgin, Gajim, and Adium.

AdiumX:
http://trac.adiumx.com/ticket/10353

Pidgin: ASCII control characters cause problems with libpurple clients
http://developer.pidgin.im/ticket/6031

Show
Ilan Rabinovitch added a comment - Would it be possible to confirm if this is related to the issues mentioned in the Pidgin and AdiumX bug trackers? Both tickets reference, but indicate they were unable to confirm if this was the solution. I know that as of openfire 3.5.2 the invalid characters still terminate client sessions for Pidgin, Gajim, and Adium. AdiumX: http://trac.adiumx.com/ticket/10353 Pidgin: ASCII control characters cause problems with libpurple clients http://developer.pidgin.im/ticket/6031
Hide
Permalink
Thoralf Will added a comment -

Still (again?) an issue with 3.6.0a
When sending something as simple as <ctrl>-<alt>-a in Adium the receiving side will disconnect within the next 2 seconds.

Show
Thoralf Will added a comment - Still (again?) an issue with 3.6.0a When sending something as simple as <ctrl>-<alt>-a in Adium the receiving side will disconnect within the next 2 seconds.
Hide
Permalink
Daryl Herzmann added a comment -

reopening.

Show
Daryl Herzmann added a comment - reopening.
Hide
Permalink
Ilan Rabinovitch added a comment -

So a fix was found and is available in 3.6.5?

Show
Ilan Rabinovitch added a comment - So a fix was found and is available in 3.6.5?
Hide
Permalink
Daryl Herzmann added a comment -

Hi,

Unfortunately, no. The ticket was just bumped against the next unreleased release .

daryl

Show
Daryl Herzmann added a comment - Hi, Unfortunately, no. The ticket was just bumped against the next unreleased release . daryl
Hide
Permalink
Steve Alligood added a comment -

Bump. This issue is constantly causing issues with over 200 users constantly getting disconnected and auto reconnecting.

Show
Steve Alligood added a comment - Bump. This issue is constantly causing issues with over 200 users constantly getting disconnected and auto reconnecting.
Hide
Permalink
Guenther Niess added a comment - - edited

Either this or the JM-1421 issue is invalid. I'm not sure which one.

Show
Guenther Niess added a comment - - edited Either this or the JM-1421 issue is invalid. I'm not sure which one.
Hide
Permalink
Ilan Rabinovitch added a comment -

@Guenther, I do not believe these 2 issues contradict each other. JM-1421 is indicating the sender of invalid XML should be disconnected. In the case of this bug OF-91, invalid XML is sent and the recipient is disconnected.

Show
Ilan Rabinovitch added a comment - @Guenther, I do not believe these 2 issues contradict each other. JM-1421 is indicating the sender of invalid XML should be disconnected. In the case of this bug OF-91 , invalid XML is sent and the recipient is disconnected.
Hide
Permalink
Daryl Herzmann added a comment -

Here's an example stanza that causes problems:

 
<message type="groupchat" id="purple3826142f" 
to="nwsbot@server/twisted_words" 
from="mlbchat@conference.server/user">
<body>Bad Character is: &#3; </body>
</message>
Show
Daryl Herzmann added a comment - Here's an example stanza that causes problems: <message type= "groupchat" id= "purple3826142f" to= "nwsbot@server/twisted_words" from= "mlbchat@conference.server/user" > <body> Bad Character is: &#3; </body> </message>
Hide
Permalink
Guus der Kinderen added a comment -

A fix for this issue is available in the just released beta of Openfire 3.7.0

Show
Guus der Kinderen added a comment - A fix for this issue is available in the just released beta of Openfire 3.7.0
Hide
Permalink
Kevin Stange added a comment -

This issue doesn't seem to be fixed, because the server is still passing invalid control characters to clients if it receives them in MUCs in version 3.7.0.

Show
Kevin Stange added a comment - This issue doesn't seem to be fixed, because the server is still passing invalid control characters to clients if it receives them in MUCs in version 3.7.0.

People

  • Assignee:
    Guus der Kinderen
    Reporter:
    Gaston Dombiak
Vote (2)
Watch (9)

Dates

  • Created:
    Updated:
    Resolved: