Risk
7/8/2013
11:48 AM
Connect Directly
RSS
E-Mail
50%
50%

Encrypted IM Tool Vulnerable To Eavesdropping

Bugs in instant messaging encryption tool Cryptocat left users' group chats vulnerable to eavesdropping for over a year, says security researcher.

The Syrian Electronic Army: 9 Things We Know
(click image for larger view)
The Syrian Electronic Army: 9 Things We Know
Cryptocat, a free tool designed to encrypt online chats, has been updated to fix errors that would have allowed an attacker to eavesdrop on chats. The vulnerability resulted from developers using below-minimum public key sizes or iterations. As a result, anyone who used a vulnerable version of Cryptocat to hold a group conversation, or who communicated with anyone using the software, could have had their communications easily intercepted.

That warning was sounded by security researcher Steve Thomas, who detailed the errors in a blog post. "If you used group chat in Cryptocat from Oct. 17th, 2011 to June 15th, 2013, assume your messages were compromised," he said. "Also if you or the person you are talking to has a version from that time span, then assume your messages are being compromised."

Thomas built a tool he calls DecryptoCat, which "cracks the ECC public keys generated by Cryptocat versions 1.1.147 through 2.0.41" in about a day, he said. Using the information generated by the tool, it would then take just a few minutes to crack any vulnerable Cryptocat key. Based on the coding errors he found, Thomas had harsh words for the chat tool's developers, who he labeled as being "incompetent." "I feel bad about calling them incompetent, but it is true. If you mess up in all the places I cared to check ... that's incompetence," he said.

[ Need an encryption how-to? Read 5 Rules For (Almost) Painless Encryption. ]

In response, Cryptocat issued an apology, and said that the bug detailed by Thomas -- which they claimed left users' communications vulnerable for only seven months -- was rapidly fixed. "The vulnerability was quickly resolved and an update was pushed," said the Cryptocat development blog post. "We sincerely thank Steve for his invaluable effort."

The developers emphasized that it's impossible to keep software entirely free from bugs. "Bad bugs happen all the time in all projects," they said. "Cryptocat is not any different from any of the other notable privacy, encryption and security projects, in which vulnerabilities get pointed out on a regular basis and are fixed. Bugs will continue to happen in Cryptocat, and they will continue to happen in other projects as well. This is how open source security works."

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Listen Now The Best of the Rest of Black Hat: The Enterprise View
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.