A 19-year-old man from London, Ontario, has been charged in connection with a hack against the Canadian Revenue Agency (CRA) website which leaked 900 social insurance numbers, and caused the website to shut down for four days.
Stephen Arthuro Solis-Reyes was apprehended by the London Police Service and the RCMP’s National Division Integrated Technological Crime Unit in connection with the attack which exploited the serious security vulnerability known as the Heartbleed bug.
Solis-Reyes, who is a student at Western University, had his computer equipment seized by the authorities and a search was conducted at his residence.
He now faces one count of Unauthorized Use of Computer and one count of Mischief in Relation to Data contrary to Sections 342.1(1)(a) and 430(1.1) of the Criminal Code, and is scheduled to appear in court in Ottawa on July 17th.
Regardless of what precisely happened in this case (which is now a matter for the Canadian legal system), it should go without saying that exploiting vulnerabilities to gain unauthorised access to data and computer systems is unwise at the best at times, and particularly foolhardy if your intended victim belongs to a government or involved critical infrastructure.
The authorities are hardly likely to take an understanding view of that.
If you believe that a website or service is poorly secured, the correct approach is to disclose the vulnerability responsibly and not put innocent people at risk by exposing their data.
By the way, it’s important to note that Solis-Reyes is not being accused of “causing” the Heartbleed bug or – as some poorly informed media will no doubt portray it – of having creating the “Heartbleed virus”.
Heartbleed isn’t a virus. It’s a bug caused by a programmer, and it was introduced into the OpenSSL code accidentally.
Unfortunately the Heartbleed bug can be exploited relatively easily by anyone on the internet, if they know how, to steal information from vulnerable services. Solis-Reyes is simply accused of having exploited the bug, which is something that many many other people have done.
- Up to 50 million Android devices could be vulnerable to Heartbleed attack. Here’s how to check yours
- Heartbleed claims British mums and Canadian tax payers as victims
- Heartbleed bug *can* expose private SSL keys
- The NSA knew about Heartbleed bug for two years, claims report
- Heartbleed bug explained by xkcd in a way anyone can understand
- In the wake of Heartbleed, watch out for phishing attacks disguised as password reset emails
- Here’s some really bad Heartbleed bug advice about changing your passwords
- Heartbleed OpenSSL bug: An FAQ for Mac, iPhone and iPad users
- Did the Heartbleed bug leak your Yahoo password?
- The Heartbleed bug: serious vulnerability found in OpenSSL cryptographic software library