Risk
7/8/2013
11:48 AM
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
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-7441
Published: 2015-05-29
The modern style negotiation in Network Block Device (nbd-server) 2.9.22 through 3.3 allows remote attackers to cause a denial of service (root process termination) by (1) closing the connection during negotiation or (2) specifying a name for a non-existent export.

CVE-2014-9727
Published: 2015-05-29
AVM Fritz!Box allows remote attackers to execute arbitrary commands via shell metacharacters in the var:lang parameter to cgi-bin/webcm.

CVE-2015-0200
Published: 2015-05-29
IBM WebSphere Commerce 6.x through 6.0.0.11 and 7.x before 7.0.0.8 IF2 allows local users to obtain sensitive database information via unspecified vectors.

CVE-2015-0751
Published: 2015-05-29
Cisco IP Phone 7861, when firmware from Cisco Unified Communications Manager 10.3(1) is used, allows remote attackers to cause a denial of service via crafted packets, aka Bug ID CSCus81800.

CVE-2015-0752
Published: 2015-05-29
Cross-site scripting (XSS) vulnerability in Cisco TelePresence Video Communication Server (VCS) X8.5.1 allows remote attackers to inject arbitrary web script or HTML via a crafted URL, aka Bug ID CSCut27635.

Dark Reading Radio
Archived Dark Reading Radio
After a serious cybersecurity incident, everyone will be looking to you for answers -- but you’ll never have complete information and you’ll never have enough time. So in those heated moments, when a business is on the brink of collapse, how will you and the rest of the board room executives respond?