{"id":3546,"date":"2024-05-13T17:24:27","date_gmt":"2024-05-13T22:24:27","guid":{"rendered":"https:\/\/www.darkreading.com\/vulnerabilities-threats\/heartbleed-when-is-it-good-to-name-a-vulnerability"},"modified":"2024-05-13T17:24:27","modified_gmt":"2024-05-13T22:24:27","slug":"heartbleed-when-is-it-good-to-name-a-vulnerability","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2024\/05\/13\/heartbleed-when-is-it-good-to-name-a-vulnerability\/","title":{"rendered":"Heartbleed: When Is It Good to Name a Vulnerability?"},"content":{"rendered":"
<\/a><\/div>\n
<\/div>\n

Back in April 2014, researchers uncovered a <\/span>serious vulnerability in OpenSSL<\/a><\/span>. There are many serious vulnerabilities, but this one was particularly bad, with security expert Bruce Schneier calling it “catastrophic.” On his blog, Schneier wrote, “<\/span>On the scale of 1 to 10, this is an 11<\/a><\/span>.” The Tor Project <\/span>issued a similarly stark warning<\/a><\/span>, “If you need strong anonymity or privacy on the Internet, you might want to stay away from the Internet entirely for the next few days while things settle.” <\/span><\/p>\n

The official name of the vulnerability was <\/span>CVE-2014-0160<\/a><\/span>, but most people know its name: Hearbleed.<\/span><\/p>\n

The Finnish company Codenomicon, which discovered the vulnerability alongside Google’s Neel Mehta, anticipated the magnitude of the issue and decided to give the flaw a name to call attention to it. Codenomicon designed a logo and launched a <\/span>website<\/a><\/span> with resources to help people address the issue quickly.<\/span><\/p>\n

“It was a pretty serious vulnerability, and that’s why we thought it would be a good idea to have a campaign around it with information,” says David Chartier, who was Codenomicon’s CEO at that time (Codenomicon was later acquired by Synopsys). “We thought it would make everybody’s life easier if we put a name on it.”<\/span><\/p>\n

Herralan Ossi<\/a><\/span>, one of the company’s security specialists, coined the name Heartbleed, an allusion to <\/span>heartbeat<\/span><\/span>, an element of the TLS\/SSL protocol. The heartbeat allows two computers to confirm they are connected to each other even if there’s no data being transferred between them. The first computer sends a <\/span>heartbeat message<\/span><\/span>, or an encrypted data packet, to the other computer at regular intervals, and the second computer returns an identical packet to confirm the connection. The Heartbleed flaw, however, allows attackers to read server memory and send additional information, or “bleeding out data,” as Chartier puts it. This way, attackers can extract sensitive information such as passwords and private keys.<\/span><\/p>\n

The impact was widespread, as <\/span>many companies<\/a><\/span> \u2014 a list which included Amazon Web Services, Dropbox, GitHub, Google, Instagram, LassPass, Minecraft, OKCupid, Netflix, Pinterest, Reddit, SoundCloud, Tumblr, Wikipedia, Yahoo and Youtube, to name just a few \u2014 announced that their servers were vulnerable and recommended users to update their passwords.<\/span><\/p>\n

“This huge vulnerability needed a striking mark,” the logo\u2019s designer, Leena Snidate, told <\/span>Fast Company<\/a><\/span> at that time. “The colour choice was immediate for me\u2013deep blood red.”<\/span><\/p>\n

The Branded Vulnerabilities Trend<\/h2>\n

In the case of Heartbleed, branding the flaw with a name and the logo helped get media attention and was successful in raising awareness around the issue. A <\/span>Pew Research Center<\/a><\/span> survey from April 2014 (within weeks of the vulnerability being disclosed) showed that 64% of internet users were aware of the bug, 39% of users took actions to secure their online accounts such as changing passwords, and 29% felt their personal information was put at risk because of the bug.<\/span><\/p>\n

Some organizations quickly patched their systems, while others took longer to respond. Ten years later, there are still around 60,000 servers running Heartbleed OpenSSL around the world, according to Chartier. He recommends companies know their attack surface better and test thoroughly the open-source tools they use.<\/span><\/p>\n

Heartbleed was among the first vulnerabilities to be branded with a name and logo, a practice later embraced by other researchers for other vulnerabilities. While some followed Codenomicon’s strategy to highlight serious threats, others applied catchy names to less critical, mundane bugs. Some names were downright silly, such as <\/span>POODLE<\/a><\/span>, <\/span>FREAK<\/a><\/span>, <\/span>Badlock<\/a><\/span>, <\/span>Thrangrycat<\/a><\/span> (which was also named using three angry cat emojis) and <\/span>Pork Explosion<\/a><\/span>.<\/span><\/p>\n

The branded vulnerabilities trend prompted many in the information security community to raise their eyebrows. In <\/span>an April Fool’s Day blog post in 2015<\/a><\/span>, Brian Gorenc, Trend Micro’s vice president of Threat Research, offered “two hours of graphic design work to create a logo specific to your bug,” as part of what has been dubbed the “No More Ugly Bugs” movement.<\/span><\/p>\n

Sometimes, the name of the bug was blown out of proportion. “[N]ot every named vulnerability is a severe vulnerability despite what some researchers want you to think,” <\/span>wrote<\/a><\/span> Leigh Metcalf for Carnegie Mellon’s Software Engineering Institute blog. “Sensational names are often the tool of the discoverers to create more visibility for their work.”<\/span><\/p>\n

This trend of choosing dramatic names for vulnerabilities has sparked discussions about the balance between necessary caution and excessive hype. “You can go overboard with branding,” says Mikko Hypp\u00f6nen, Chief Research Officer at WithSecure. “Every mundane vulnerability doesn’t need a website and a logo \u2013 even though marketing departments would like that.”<\/span><\/p>\n

Balance Between Marketing and Security<\/span><\/h2>\n

Deciding to name a vulnerability or not is a tricky call to make. “For every Heartbleed, there are just a bunch of bugs that are not as serious as people think they are,” says Dustin Childs, head of Threat Awareness at Trend Micro’s Zero Day Initiative (ZDI). “We need to be careful with what we name, and with how we promote it. It’s very easy to go from doing well for the community to overpromoting something for personal gain.”<\/span><\/p>\n

Childs argues that vulnerabilities with widespread exploitation or those impacting multiple products deserve names. However, he believes that bugs affecting specific systems should simply be referred to by their CVEs. “I don’t think one bug affecting Windows should be named. I don’t think one bug affecting Mac OS should be named,” Childs says.<\/span><\/p>\n

ZDI does not name their bugs because that’s not a line the organization wants to cross, “even though it is clear sometimes that line needs to be crossed,” Childs says. <\/span><\/p>\n

Childs agrees, though, that in the case of serious vulnerabilities like Heartbleend or Log4j, using a name instead of a CVE makes a difference. “CVEs are very useful from a documentation perspective,” he says. “But when you’re talking to your C-suite, to folks who are making decisions but aren’t necessarily technical, it’s easier to have a name to call something. It makes the conversation simpler.”<\/span><\/p>\n

Naming vulnerabilities also creates problems, especially when the name makes the bug seem either too benign or too scary. “No sysadmin likes to patch unnecessarily or before understanding the scope of a vulnerability and the options for mitigating exploits,” says Sean O’Brien, lecturer in cybersecurity at Yale Law School and founder of Yale Privacy Lab.<\/span><\/p>\n

It is why sysadmins and security experts responsible for patching vulnerabilities need to consider their priorities carefully and avoid the pitfall of rushing to patch a bug solely because it has a sinister name and is in the news.<\/span><\/p>\n

O’Brien adds that, when choosing a name for a vulnerability, organizations should be careful with humor, which could downplay the seriousness of a threat or even make people angry. “That’s especially true when bias about the origin of a threat creeps into the name,” he says. “I don’t think most American security professionals would warm up to a name like <\/span>Crappy Eagle<\/span><\/span> about a vulnerability that likely emerged from an NSA arsenal.”<\/span><\/p>\n

In recent years, various organizations have started to think that the name should reflect the seriousness of the threat, as well as how the bug can be exploited. One initiative that aimed to settle the issue was <\/span>Vulnonym<\/a><\/span>, which attempted to give researchers guidance in naming CVEs. This initiative, however, had limited success. <\/span><\/p>\n

“I don’t think we need a central org that names vulnerabilities,” security researcher Martijn Grooten, former editor of the Virus Bulletin, says. “For most practical purposes, CVEs work just fine.”<\/span><\/p>\n

Ten years after Heartbleed, the security community continues to grapple with naming vulnerabilities. “It’s always going to be tough to strike that balance as security and marketing often have different interests,” Grooten adds. “The important thing for me will be to always make claims that are accurate.”<\/span><\/p>\n

Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Back in April 2014, researchers uncovered a serious vulnerability in<\/p>\n","protected":false},"author":12,"featured_media":3547,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[809],"class_list":["post-3546","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-dark-reading"],"featured_image_urls":{"full":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/05\/heartbleed-when-is-it-good-to-name-a-vulnerability.jpg?fit=1000%2C563&ssl=1",1000,563,false],"thumbnail":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/05\/heartbleed-when-is-it-good-to-name-a-vulnerability.jpg?resize=150%2C150&ssl=1",150,150,true],"medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/05\/heartbleed-when-is-it-good-to-name-a-vulnerability.jpg?fit=300%2C169&ssl=1",300,169,true],"medium_large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/05\/heartbleed-when-is-it-good-to-name-a-vulnerability.jpg?fit=640%2C360&ssl=1",640,360,true],"large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/05\/heartbleed-when-is-it-good-to-name-a-vulnerability.jpg?fit=640%2C360&ssl=1",640,360,true],"1536x1536":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/05\/heartbleed-when-is-it-good-to-name-a-vulnerability.jpg?fit=1000%2C563&ssl=1",1000,563,true],"2048x2048":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/05\/heartbleed-when-is-it-good-to-name-a-vulnerability.jpg?fit=1000%2C563&ssl=1",1000,563,true],"chromenews-featured":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/05\/heartbleed-when-is-it-good-to-name-a-vulnerability.jpg?fit=1000%2C563&ssl=1",1000,563,true],"chromenews-large":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/05\/heartbleed-when-is-it-good-to-name-a-vulnerability.jpg?resize=825%2C563&ssl=1",825,563,true],"chromenews-medium":["https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/05\/heartbleed-when-is-it-good-to-name-a-vulnerability.jpg?resize=590%2C410&ssl=1",590,410,true]},"author_info":{"display_name":"Dark Reading","author_link":"https:\/\/ddi.mohflo.net\/index.php\/author\/darkreading\/"},"category_info":"Uncategorized<\/a>","tag_info":"Uncategorized","comment_count":"0","jetpack_featured_media_url":"https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2024\/05\/heartbleed-when-is-it-good-to-name-a-vulnerability.jpg?fit=1000%2C563&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/3546","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/comments?post=3546"}],"version-history":[{"count":0,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/3546\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media\/3547"}],"wp:attachment":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media?parent=3546"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/categories?post=3546"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/tags?post=3546"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}