Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-25540

Use more secure encryption algorithm for AESBinaryManager

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.3
    • Component/s: BlobManager
    • Impact type:
      Data Persistence Change
    • Upgrade notes:
      Hide

      Before Nuxeo 10.3, the encryption used was based on AES/CBC/PKCS5Padding which has been found to be insecure (susceptible to padding oracle attacks).

      Starting with Nuxeo 10.3, a more secure encryption algorithm, AES/GCM/NoPadding, is used. If you're migrating data from an earlier version and therefore still need to use the old insecure encryption algorithm, you must add the option useInsecureCipher=true to the nuxeo.core.binarymanager_key in nuxeo.conf.

      See https://doc.nuxeo.com/nxdoc/implementing-encryption/#filesystem-aes-encryption for details.

      Show
      Before Nuxeo 10.3, the encryption used was based on AES/CBC/PKCS5Padding which has been found to be insecure (susceptible to padding oracle attacks). Starting with Nuxeo 10.3, a more secure encryption algorithm, AES/GCM/NoPadding , is used. If you're migrating data from an earlier version and therefore still need to use the old insecure encryption algorithm, you must add the option useInsecureCipher=true to the nuxeo.core.binarymanager_key in nuxeo.conf . See https://doc.nuxeo.com/nxdoc/implementing-encryption/#filesystem-aes-encryption for details.
    • Sprint:
      nxFG 10.3.3
    • Story Points:
      2

      Description

      AESBinaryManager currently uses AES/CBC/PKCS5Padding which has been discovered to be susceptible to padding oracle attacks (https://find-sec-bugs.github.io/bugs.htm#PADDING_ORACLE, https://en.wikipedia.org/wiki/Padding_oracle_attack#Padding_oracle_attack_on_CBC_encryption).

      It should be replaced by the more secure AES/GCM/NoPadding.

      NOTE that this means that previously-encrypted data will not be readable anymore. Compatibility is provided to keep using the old insecure encryption mode (see upgrade notes).

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours
                  2h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.