1

Atlassian recently introduced a standalone installer that installs JIRA, along with its own JRE. Unfortunately the JRE Atlassian bundles with this installer is 1.6.0_26, whereas the current version of the JRE is 1.6.0_29. This is potentially concerning given there were vulnerabilities in _26 that were fixed in the subsequent versions. We are currently using the bundled-installer version of JIRA and one contractor has recommended we ditch this for the system-installed JRE.

My question is this: what is the actual security risk of continuing to use the _26 version of the JRE included in the bundled installer? There is no public access to our install of JIRA (only about 20 employees and contractors can login to our JIRA) and it's only accessible on a subdomain of a domain at which there's no publicly-available website. If there's a not insignificant risk inherent in sticking with the older JRE, why hasn't Atlassian upgraded the default JRE?

1 Answer 1

0

According to an official risk matrix from Oracle the security risk is quite high. Of course your environment is isolated from an external attacker but security is never too much. I guess Atlassian just did not have enough time to replace the bundled JRE yet, maybe it was not a top priority task in their release plan.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .