{"id":15138,"date":"2016-04-25T15:33:24","date_gmt":"2016-04-25T15:33:24","guid":{"rendered":"https:\/\/kasperskydaily.com\/b2b\/?p=5495"},"modified":"2020-02-27T04:03:00","modified_gmt":"2020-02-26T17:03:00","slug":"jboss-flaw","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com.au\/blog\/jboss-flaw\/15138\/","title":{"rendered":"3.2m servers are possible targets for a ransomware campaign"},"content":{"rendered":"<p>3.2 million servers fall victim to an old and now heavily exploited vulnerability. Cisco\u00a0<a href=\"https:\/\/threatpost.com\/3-2-million-servers-vulnerable-to-jboss-attack\/117465\/\" target=\"_blank\" rel=\"noopener nofollow\">released<\/a> a formidable heads-up earlier this month, stating that over 3\u00a0million servers are vulnerable to the JBoss flaw, with many already backdoored.<\/p>\n<p>JBoss (currently WildFly) <a href=\"https:\/\/en.wikipedia.org\/wiki\/WildFly\" target=\"_blank\" rel=\"noopener nofollow\">is middleware produced by Red Hat<\/a> that includes enterprise-class software used to create and integrate applications, data and devices, and automate business processes. The vulnerability in question is five years old (i.e. really old), and the patch has been available since 2010. Red Hat has even renamed JBoss since then.<\/p>\n<p>Still, as an example of \u201c<a href=\"https:\/\/business.kaspersky.com\/a-story-about-an-undead-protocol-and-old-junk\/4185\/\" target=\"_blank\" rel=\"noopener nofollow\">IT renewal reluctance<\/a>\u201c, a malady very characteristic for larger businesses, the old and vulnerable versions of JBoss are still around because of the custom applications based on those versions.<\/p>\n<p>This old flaw has been used by the actors behind the massive ransomware campaign <a href=\"https:\/\/threatpost.com\/new-server-side-ransomware-hitting-hospitals\/117059\/\" target=\"_blank\" rel=\"noopener nofollow\">codenamed SamSam<\/a>. Unlike many others, SamSam is targeting servers specifically. As of the end of March, hospitals were the primary victims of the attacks, however later it was discovered that hackers have used the very same vulnerability to backdoor a large number of schools (primarily in the U.S.).<\/p>\n<p><a href=\"https:\/\/threatpost.com\/3-2-million-servers-vulnerable-to-jboss-attack\/117465\/\" target=\"_blank\" rel=\"noopener nofollow\">According to Threatpost<\/a>, the hardest hit have been K-12 schools running library management software called Destiny by Follett.<\/p>\n<p>Attackers are using a JBoss-specific exploit tool called Jexboss to compromise servers. According to Cisco Talos researchers, the JBoss vulnerability has been used to drop a number of webshells and backdoors, including \u201cmela\u201d, \u201cshellinvoker\u201d, \u201cjbossinvoker\u201d and \u201cjbot,\u201d among others, meaning the machines have likely been compromised over and over.<\/p>\n<p>Server-side ransomware is, mildly put, a troubling\u00a0development. Unlike the more common type where the endpoints are hit, a ransomware attack requires at least some cooperation from a gullible user. Server-side ransomware does not require it: attackers have many\u00a0chances to go in undetected, while the damage inflicted to the internal infrastructure of the affected company may be much more extensive than with \u201ccommon\u201d ransomware.<\/p>\n<p>SamSam actors successfully identified the key data systems for them to encrypt, to have more chances for successful extortion.<\/p>\n<p>Hospitals were targeted because of a popular perception they have substandard cybersecurity and often rely on obsolete technology (Securelist recently published <a href=\"https:\/\/securelist.com\/blog\/research\/74249\/hospitals-are-under-attack-in-2016\/\" target=\"_blank\" rel=\"noopener\">a great piece on hospital security<\/a> \u2013 things aren\u2019t encouraging there).<\/p>\n<p>However, medical facilities \u2013 and schools \u2013 aren\u2019t the only possible targets for attacks like these, and we\u2019ll definitely hear more about it. 3.2 million vulnerable servers is a formidable figure on its own.<\/p>\n<p>JBoss vulnerability in question is described at <a href=\"https:\/\/access.redhat.com\/security\/cve\/cve-2010-0738\" target=\"_blank\" rel=\"noopener nofollow\">this link<\/a>, along with the appropriate patch.\u00a0Follett company also <a href=\"http:\/\/follett.com\/statement\/destiny-jboss\/\/\" target=\"_blank\" rel=\"noopener nofollow\">released<\/a> its own advisory on a problem with Destiny, which offers the following recommendations.<\/p>\n<ul>\n<li>Check out, whether a webshell (possibly more) have been installed on the suspicious server.<\/li>\n<li>If there are any, the external access to the server must be cut off as soon as possible.<\/li>\n<li>Follett recommends to re-image the system and install updated versions of software, if at all possible.<\/li>\n<li>If not, the best option is to restore from a backup prior to the compromise, and then upgrade the server to a non-vulnerable version before returning it to production.<\/li>\n<li>Destiny users receive updates automatically; a correct patch installation removes all backdoor shells.<\/li>\n<\/ul>\n<p>Follett also recommends using a reputable security software. Kaspersky Lab has appropriate products for both <a href=\"https:\/\/www.kaspersky.com\/business-security\/small-to-medium-business\" target=\"_blank\" rel=\"noopener nofollow\">small to\u00a0medium businesses<\/a>\u00a0and <a href=\"https:\/\/www.kaspersky.com\/enterprise-security\" target=\"_blank\" rel=\"noopener nofollow\">enterprises<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A new strain of ransomware targets servers which is, mildly put, a troubling development. <\/p>\n","protected":false},"author":209,"featured_media":15410,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,2994],"tags":[2412,420,640,2413],"class_list":{"0":"post-15138","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-smb","9":"tag-jboss","10":"tag-ransomware","11":"tag-vulnerability","12":"tag-wildfly"},"hreflang":[{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/jboss-flaw\/15138\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/jboss-flaw\/15138\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/jboss-flaw\/15138\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com.au\/blog\/tag\/jboss\/","name":"JBoss"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts\/15138","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/users\/209"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/comments?post=15138"}],"version-history":[{"count":3,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts\/15138\/revisions"}],"predecessor-version":[{"id":26865,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts\/15138\/revisions\/26865"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/media\/15410"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/media?parent=15138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/categories?post=15138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/tags?post=15138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}