Two critical severity CVE’s were announced in October for the popular collaboration platform Atlassian Confluence. The first bug, CVE-2023-22515 was announced on October 4th, and classified as a CVSS 10! CISA published a CyberSecurity Advisory on October 5th which was quickly followed by a similar advisory from the ACSC here in Australia.

Quickly after that, Atlassian updated the CVE to say that this zero-day was being actively exploited in the wild by a nation state actor. You can read Atlassian’s advisory here: https://confluence.atlassian.com/security/cve-2023-22515-privilege-escalation-vulnerability-in-confluence-data-center-and-server-1295682276.html

Additionally, you can read CISA’s advisory here: https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-289a and the ACSC advisory here: https://www.cyber.gov.au/about-us/view-all-content/alerts-and-advisories/multiple-vulnerabilities-atlassian-confluence-data-center-and-server

What services are affected?

Thankfully, this CVE-2023-22515 only affected Confluence Server and Data Center products, and not the cloud SaaS versions of Confluence. Moreover, it only affected versions 8.0.x to 8.5.3. This limited the scope significantly, but because of the type of product that Confluence is, there are a LOT of large organizations that run Confluence as a self-hosted server. And many of them, unfortunately, are not used to patching Confluence routinely. This is where the problem lies.

Then, last week another Confluence bug was announced. Initially, it was “only” a 9.1, but here’s the important part:  This new bug affected EVERY version of Confluence ever released!   This CVE 2023-22518, affected Data Center and Server products only, like the first bug, but the number of Confluence versions affected was MUCH larger. All versions of Confluence from 1.x to 8.5.3 were affected. This meant that many of the larger organizations that weren’t vulnerable to the first vulnerability because they hadn’t updated from version 7.x, were in fact vulnerable to this second bug.

Then on November 7th, 2023, Atlassian upgraded CVE-2023-22518 to a CVSS 10!  Turns out that 22518 is more similar to 22515 than initially though and allows you to create administrator accounts in a similar way.  There are multiple POCs in the wild that appear to work, and Atlassian has detected that this bug has been packaged into ransomware.

This means there are now TWO CVSS 10 bugs we have to address.

Why is this such a big deal?

Confluence, Jira, and other developer focused tools have a long history of being available outside of the VPN perimeter. This is often because the devs involved want to be able to use these tools when working from home, or via their own laptops. Because of this, even self-hosted servers like Confluence, Jira and Bitbucket can be really juicy targets to malicious actors because these servers host really sensitive intellectual property, and are often poorly defended.

How did SecureStack get involved?

SecureStack maintains a set of deception services pretending to be developer focused tools like Confluence. This allows us to gain insight into new attacks and trends against these hosted services. Over the last two years we’ve used this data to help us build better defenses and new detections for attack types. These detections are built into our platform and we make these available to any paying customers.

Over the last several weeks SecureStack saw a noted increase in the amount of traffic related to scanning for public facing Confluence servers, and the types of attacks were new. They were targeting specific endpoints and routes within Confluence. Based on user agent data we could see that much of this scanning was probably automated.

Sure enough, a quick search of GitHub showed there were multiple projects and POCs for CVE-2023-22515.   Project Discovery quickly built a Nuclei template which went live on October 10th: https://github.com/projectdiscovery/nuclei-templates/commit/0471ab31c7ef32000f45a5d2f59b18311f39dfeb

Quick legal disclaimer

The purpose of this blog post is to help us understand how widespread these vulnerabilities are.  Exploiting these vulnerabilities and server products is illegal.   The data I reference here is based on public websites and the data is collected using simple HTTP requests (GETs) and responses looking for things like headers, meta tags and body content.

Now with that out of the way, let’s dig into this…

How big is the collective attack surface these two CVEs?

Well, let’s start with collecting some data around public facing Confluence servers. There are two steps to this:

First, find targets!  Second, test what versions of Confluence they are running. For the first part, let’s use Shodan and SecurityTrails as they both can give us a large number of Confluence servers quickly.

The Shodan CLI is probably the best way to collect data for this kind of project. Shodan allows you to use data in the HTML or headers to search by. Here’s a CLI command that will collect a list of Confluence servers globally:

shodan search –fields ip_str,hostnames http.component:”atlassian confluence”

How can you identify what’s “real” data from Shodan?

Shodan is an amazing platform and I use it almost every day, however it’s important to know how it categorizes and displays data to really understand whether to trust its data. For example, because it focuses on ports as a primary key:value primitive it groups “results” by ports rather than by IP which is not obvious to you when you use the web UI.  If you scan a single IP or domain name and then download or search the results, Shodan displays ports as individual “results”.  Said a different way, one IP address will have multiple “results” in Shodan.

All you have to do to prove this point is to sort by unique IP addresses and hostnames in the Shodan data and you’ll see the real numbers:

SecurityTrails data can help build out your dataset

In addition, to the data you get from Shodan, it can help to search DNS records for keywords related to your target.  SecurityTrails is comprised of a static list of historical DNS entries and as such you need to sort and test for relevancy.

So for Confluence, some good keywords are: confluence, support, wiki, jira, knowledgebase, kb, etc

Here are some recent results from the free version of securitytrails.com for “confluence”:

How do we identify if Confluence is present and is vulnerable?

Both CVE-2023-22515 and 22518 only affect Confluence data center and server products, so all Atlassian Cloud instances are not affected.  If you don’t know which version you are using, typically Atlassian Cloud uses an atlassian.net URL to login.

Once you have refined your target list, you need to identify what version of Confluence they’re running.  The CVE advisories list the specific versions that are affected by each of the vulnerabilities.  Finding the version of Confluence is relatively easy to do because Atlassian has added several metadata tags to their products which you can test for.

The “confluence-base-url” is a meta tag added to Confluence to clarify the hostname it is using.  This is helpful in figuring out what the DNS name is if you find just the IP address on Shodan.  This is the authoratative test to determine that the service is Confluence.

<meta id=”confluence-base-url” name=”confluence-base-url” content=”https://confluence.example.com.au”>

The “ajs-version-number” tag is added to most Atlassian products and should be used as an authoratative source of the version number if “confluence-base-url” is also present.  Otherwise you might get results from Jira, Bamboo, or Bitbucket servers.

<meta name=”ajs-version-number” content=”7.13.7″> <meta name=”ajs-build-number” content=”8703″>

The “ajs-base-url” tag is added to most Atlassian products and should be checked only be used to determine the hostname if “confluence-base-url” isn’t available or wrong.

<meta name=”ajs-base-url” content=”https://confluence.example.com.au”>

Let’s use Elasticsearch to help us understand the data

Once you have the hostnames and Confluence versions data you can send the data to your data solution of choice. I tend to use Elasticsearch and ELK as I’ve been working with it for years.

My Confluence Dashboard

This dashboard isn’t complicated and really only cares about three things:  IP address, hostname, and Confluence version number.  All of my analysis relies on those three things.  If I know the version number and the hostname I use the IP address to verify this is a unique host.  This idea of a unique hosts is really important and is more complicated than it might seem but I’ll spare you the details now.

In this image, you can see there are 3323 unique hosts in this dataset.   The bar graph on the left represents how many of each vulnerable version of Confluence is in the data set.  On the right bar graph, are the secure, patched versions of Confluence.  Clearly, there are a lot less of the latter than there are of the former.

We landed on this number of 3323 servers by sorting all records by unique IP address rather than hostname.  There are a lot more hostnames in the dataset than IPs.

In the above image we can see that there are more than 18,000 records in the dataset in total.  This includes results from Shodan for ports attached to the same IP address and using this number would slant our data in the wrong direction.   So today we’ll be focusing on the 3300+ unique hostnames.

So, how bad is it?  

What has the impact been so far?

Active exploits of CVE-2023-22518 are happening in the wild.  Rapid7 is seeing this bug being used in multiple ways.  You can read their report here: https://www.rapid7.com/blog/post/2023/11/06/etr-rapid7-observed-exploitation-of-atlassian-confluence-cve-2023-22518/

Atlassian reported that some of their customers are seeing CVE-2023-22518 being used to deploy ransomware.  Soon after that Red Canary reported that they’ve seen this vulnerability used to deploy the Cerber ransomware strain.  You can read Red Canary’s report here:  https://redcanary.com/blog/confluence-exploit-ransomware/

We are also hearing from several of our partners that they are seeing widespread use of this vulnerability in different attack scenarios including ransomware, destructive attacks and other avenues.

So, what’s next?  Where do we go from here?!

Well, the first thing is for CISA to add CVE-2023-22518 to the KEV list.  Aha, I just checked and CISA has now done as of this evening.   Good start.

Second, if you know that you have a hosted Confluence server you might wanna go check the version number, and then immediately check if any new users have been created.  Also, look for the installation of new plugins as several threat actors have been installing malicious Confluence plugins.

Third, Greynoise is tracking several actors who are targeting CVE-2023-22518.  You can see their data and download a list of IPs and add them to your deny list:  https://viz.greynoise.io/tag/atlassian-confluence-server-authentication-bypass-attempt?days=10

Finally, if you need help determining if your org is exposed to these two critical bugs, feel free to reach out to the SecureStack team:  hello [at] securestack.com or you can use the chat function in the lower right corner of this page.

Good luck and happy hunting people!

Paul McCarty

Founder of SecureStack

DevSecOps evangelist, entrepreneur, father of 3 and snowboarder

Forbes Top 20 Cyber Startups to Watch in 2021!

 Mentioned in KuppingerCole's Leadership Compass for Software Supply Chain Security!

Software supply chain attacks have grown exponentially over the last three years:  malicious packages, package manager corruption, continuous delivery pipeline attacks, dependency confusion, zero days in open-source software and more.  This is driving many organizations to look for better visibility across their software supply chain. 

Let’s dive in a bit to see why the problem is growing and some potential solutions.

Application complexity is increasing

The reality is that modern applications are complex and dynamic, and therefore hard to secure. They use programming languages that run entirely in the browser, they talk directly to their dependencies on the internet and they use technologies like containers, serverless and public cloud. All of these bring their own challenges, so we need visibility into all these other application components and dependencies as well. What third-party APIs and public cloud components is it using? Is it using an identity provider like Auth0 or Cognito? What infrastructure is required to make the app run? All of these things need to be understood to really be able to better represent what is in an application and how to secure it.

SBOMs can help address software supply chain risks

One way to address the risks inherent to the complex applications we are building is to use “Software Bill of Materials” also known simply as “SBOM”.  At its simplest, a SBOM is a list of all the different component parts of an application. This typically includes several types of information about each component: Its name, who supplied the component, what license it uses, the version number, any known vulnerabilities, and a list of all the component’s dependencies.

Most SBOM tools that exist right now, focus on showing customers some of the open-source libraries that they are using in their applications.  Moreover, most SBOMs are stand-alone JSON documents and by themselves don’t provide much value.  Even worse, many SBOMs are created once and then never updated so they quickly become out of sync with the actual application they are supposed to describe.

What’s in the SBOM lifecycle?

Most SBOM advocates believe that SBOMs should be automatically created during deployment, and should be as descriptive of the actual application as possible.  To do this, organizations need to have a process that identifies applications, creates SBOMs and then makes them available for the business to gain value from.  We believe the best way to do that is to create a SBOM lifecycle policy.

There are five stages in the SBOM lifecycle: Asset discovery, application data analysis, SBOM creation, SBOM storage and SBOM searchability.

Let’s go through each of these stages one at a time.

Existing asset discovery or attack surface mapping tools can help find assets but what do you do with the list that these tools have generated?  Most of those tools don’t have any SBOM functionality, so how do you get the list of assets into your SBOM creation pipeline?  It’s better if your solution can find your assets, show them to you and allow them to create a SBOM from that same workflow.

Imagine if you had this functionality back in December 2021 when the Log4j zero-day dropped!  Wouldn’t it have been nice to go to a central place you could go and say “hey, tell me all the places that Log4j is being used and what versions they are!”

Tying it all together

Building a complete SBOM lifecycle can be a challenge, but in the end, the value that it provides to organizations is enormous.  Simply having the ability to quickly find all the software and application components in your estate of apps is huge.   But even better, being able to query that data for vulnerable components could save organizations millions of dollars in lost productivity.  

Native SBOM lifecycle

You can build your own SBOM lifecycle or alternatively, SecureStack automates the whole process from end to end.  Our platform delivers all stages of the SBOM lifecycle in a fully integrated solution that is incredibly easy to onboard. Our platform provides an end-to-end SBOM solution that helps organizations address software supply chain risks holistically.  We find all your application assets, automate the creation of your SBOMs, store them for you in a secure central repository, and make them searchable.

Our role-based access control means you can give your security and engineering teams access to those pieces of the SBOM lifecycle that they need.

Paul McCarty

Founder of SecureStack

DevSecOps evangelist, entrepreneur, father of 3 and snowboarder

Forbes Top 20 Cyber Startups to Watch in 2021!

 Mentioned in KuppingerCole's Leadership Compass for Software Supply Chain Security!

The FDA has released new cybersecurity regulations for medical device suppliers

The Food and Drug Administration (FDA) has announced that medical devices must now meet specific cybersecurity guidelines. Cyber-attacks against healthcare organizations increased by 74% last year, and attacks on the software supply chain have increased an average of 610% per year since 2020.

These new security requirements were introduced as part of a $1.7 trillion federal omnibus spending bill signed by President Joe Biden in December. The FDA must update its medical device cybersecurity guidance every two years.

What’s in the new requirements?

Device manufacturers must now submit plans to monitor, identify, and address post-market cybersecurity vulnerabilities and exploits, including coordinated vulnerability disclosures and plans, within a reasonable timeframe.  Suppliers must also make security updates and patches available on a regular schedule and in critical situations

The requirement for vulnerability disclosure is in line with what we are seeing from NIST, CIS and other standards organizations.  Unfortunately, many medical device suppliers do NOT currently have vulnerability disclosure programs.

If you want to learn more about DevSecOps and how it can help your teams embed security into the software development processes you can check out our blog post.

Medical device suppliers must also include a software bill of materials (SBOM) containing all commercial, open-source, and off-the-shelf software components while complying with other FDA requirements “to demonstrate reasonable assurance that the device and related systems are cyber secure.”

SBOMs need to be up-to-date, accurate and validated by a third party.  If you want to learn more about medical device SBOMs, you can check out our blog post on the subject.

So, how do can you address these new requirements?

Medical device suppliers who are building custom software and/or firmware will need to implement several technologies to address the new FDA requirements.  Let’s go through each of these one at a time:

• Asset discovery & management – The first place to start is with a asset discovery and management solution that will give you insight into what you have and is it internet connected.
• Application security analysis – Once you know what your assets are you need to make sure that the software you are building is secure.  Software composition (SCA) tools are a great place to start as they help you understand what open-source libraries are in your applications.
• Vulnerability management – Next up is implementing a vulnerability management platform that will find all vulnerabilities in your hardware and software and prioritize them for you.  This helps you prioritize what to focus on and what’s not really a problem.
• SBOM – The final part to addressing the FDA’s requirements is implementing an automated third-party SBOM program.  This can be added to your software development automation so that everytime a new release is built for your medical device its been tested and a SBOM has been created.

Paul McCarty

Founder of SecureStack

DevSecOps evangelist, entrepreneur, father of 3 and snowboarder

Forbes Top 20 Cyber Startups to Watch in 2021!

 Mentioned in KuppingerCole's Leadership Compass for Software Supply Chain Security!

Cyber attacks on medical devices are increasing

Cyber-attacks against healthcare organizations increased by 74% last year, and attacks on the software supply chain have increased an average of 610% per year since 2020.  These attacks can take various forms that attack the functionality and reliability of medical devices and the software that runs on these devices. This in turn, unfortunately, can lead to mistrust of the device and its manufacturer and ongoing brand damage.

Most medical devices have software running on them and often connect to software on computers, smartphones or mobile apps to share and exchange data.  Having multiple software components in these different places adds security challenges that many medical device suppliers aren’t properly prepared to address.  This is one of the reasons that the US Department of Health and Human Services (HHS) and the Food and Drug Administration (FDA) have partnered to create new regulations for medical device suppliers.

Traditionally, manufacturers of medical devices have not had visibility into what went into the software and firmware running on their devices.  This has led many organizations to try and find better ways for them, and their users, to find confidence in the security of medical equipment.

Government creates rules to address attacks

According to new government requirements, all medical device suppliers must submit a plan to monitor, identify, and address cybersecurity issues. They must also create a process that provides reasonable assurance that their device is protected. Additionally, applicants must make security updates and patches available on a regular schedule and in critical situations. Finally, they must provide the FDA with a software bill of materials, including any open-source or other software components their devices use.

SBOMs can help address software supply chain risks in medical devices

One way that medical device manufacturers can improve visibility is by implementing a Software Bill of Materials, also known as an SBOM.  An SBOM is a comprehensive list of all the software components running on a medical device.  This includes:

• Open-source and third-party software components
• Firmware and binaries
• Cloud resources
• APIs the device interacts with, or sends data to

The implementation of SBOMs is especially crucial for the medical device industry. Due to the potential risks of medical device software vulnerabilities, regulatory bodies such as the FDA, have made SBOMs mandatory for medical device manufacturers.

With an SBOM in place, manufacturers can identify vulnerabilities and take action to address them before they can be exploited by attackers. This can help reduce the risk of harm to patients and ensure that medical devices are safe and reliable.

Government and industry requirements for SBOM

• US Federal Government:  On December 29, 2022, the White House signed H.R. 2617, the Consolidated Appropriations Act 2023, which included several cybersecurity provisions.  This bill introduces new requirements for medical device manufacturers to ensure that their devices meet certain minimum cybersecurity standards. These requirements will take effect 90 days after the bill is enacted and include:
  • This involves monitoring, identifying, and addressing cybersecurity vulnerabilities and exploits that arise after a product has been released to the market. This includes coordinated vulnerability disclosure, as well as requiring the release of software and firmware updates and patches to address these vulnerabilities.
  • It also requires medical device manufacturers to provide a Software Bill of Materials (SBOM) to the FDA Secretary, which includes all off-the-shelf, open-source, and critical components used by the devices.
• FDA:  The Food and Drug Administration (FDA) has published the “Cybersecurity in Medical Devices” guidance document.  You can find all of the FDA’s guidance on cybersecurity here.
• IMDRF:  The International Medical Device Regulators Forum has published two documents about SBOM.  The first is the “Principles and Practices for Medical Device Cybersecurity” and the second is the “Principles and Practices for Software Bill of Materials for Medical Device Cybersecurity“.
• US Department of Health and Human Services:  HHS has published the “Health Industry Cybersecurity Practices: Managing Threats and Protecting Patients (HICP)” document.
• Australian Department of Health and Aged Care:  The Australian TGA has released the “Medical Device Cyber Security Guidance for Industry” document.

How do medical device suppliers get started with SBOM?

All federal agencies mentioned above believe that SBOMs should be automatically created during the software development process.  Moreover, these SBOMs should be as descriptive of the actual application running on, or connected to, the medical device it supports.  To do this, organizations need to have a process that identifies the different steps involved in software development, creates the SBOM and then makes them available for the business to gain value from.  We believe the best way to do that is to create a SBOM lifecycle policy.

There are five stages in the SBOM lifecycle: Asset discovery, application data analysis, SBOM creation, SBOM storage and SBOM searchability.

Let’s go through each of these stages one at a time.

Many SBOM tools don’t support medical device SBOMs

Most SBOM tools that exist right now, focus on showing customers some of the open-source libraries that they are using in their applications.  Moreover, most SBOMs are stand-alone JSON documents and by themselves don’t provide much value.  Even worse, many SBOMs are created once and then never updated so they quickly become out of sync with the actual device and applications they are supposed to describe.  Medical device manufacturers need to make sure their SBOMs are up-to-date and accurate.

Automate SBOMs for medical devices and client applications!

SecureStack automates the whole process of collecting data and building SBOMs from beginning to end.  We sign and attest our SBOMs so you can provide our reports and data to the government, partners, auditors, or anyone else you choose to.  Our platform delivers all stages of the SBOM lifecycle in a fully integrated solution that is incredibly easy to onboard.  We find all your application assets, automate the creation of your SBOMs, store them for you in a secure central repository, and make them searchable.

Paul McCarty

Founder of SecureStack

DevSecOps evangelist, entrepreneur, father of 3 and snowboarder

Forbes Top 20 Cyber Startups to Watch in 2021!

 Mentioned in KuppingerCole's Leadership Compass for Software Supply Chain Security!

SecureStack is excited to announce that we now support Azure DevOps through the use of our native Azure Pipelines templates!

SecureStack provides comprehensive security coverage with our brand-new Azure DevOps integration.  Our customers asked us to support Azure DevOps so we’ve delivered!  You can now generate a custom pipeline template document right from the SecureStack SaaS web portal and copy that directly into an Azure pipeline and have it work.  No changing it to work or customization is necessary.  Just drop it in and it runs!

One Pipeline: Complete security coverage

SecureStack provides complete coverage for your Azure DevOps Pipelines and the associated secure software development lifecycle (SSDLC).  As part of our native Azure DevOps Pipeline workflows we provide:

• Secrets and sensitive scanning
• Scanning for vulnerable third-party or open-source libraries
• Dynamic application security testing for any web or API endpoints
• Scanning for misconfiguration in your public cloud resources
• Asset discovery and attack surface mapping for your public assets

Once all those tests pass, SecureStack will package up a software bill of materials (SBOM) for the application environment, and there you have it: Complete Security Coverage for your SDLC!

Paul McCarty

Founder of SecureStack

DevSecOps evangelist, entrepreneur, father of 3 and snowboarder

Forbes Top 20 Cyber Startups to Watch in 2021!

 Mentioned in KuppingerCole's Leadership Compass for Software Supply Chain Security!