Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-16751

Upgrade derby to from



    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.3.1, 1.4.1, 1.5.2, 1.6.2, 2.0.0
    • 1.6.3, 2.0.1, 2.1.0
    • Build
    • None
    • All platforms and major Spark releases

    • Important


      This JIRA is to upgrade the derby version from to

      Sean and I figured that we only use derby for tests and so the initial pull request was to not include it in the jars folder for Spark. I now believe it is required based on comments for the pull request and so this is only a dependency upgrade.

      The upgrade is due to an already disclosed vulnerability (CVE-2015-1832) in derby We used https://www.versioneye.com/search and will be checking for any other problems in a variety of libraries too: investigating if we can set up a Jenkins job to check our pom on a regular basis so we can stay ahead of the game for matters like this.

      This was raised on the mailing list at http://apache-spark-developers-list.1001551.n3.nabble.com/VOTE-Release-Apache-Spark-2-0-0-RC5-tp18367p18465.html by Stephen Hellberg and replied to by Sean Owen.

      I've checked the impact to previous Spark releases and this particular version of derby is the only relatively recent and without vulnerabilities version (I checked up to the 1.3 branch) so ideally we'd backport this for all impacted Spark releases.

      I've marked this as critical and ticked the important checkbox as it's going to impact every user, there isn't a security component (should we add one?) and hence the build tag.




            aroberts Adam Roberts
            aroberts Adam Roberts
            0 Vote for this issue
            3 Start watching this issue