Extra slashes in Cipher transformation leads to NSPE instead of NSAE

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P4
    • None
    • Affects Version/s: 21
    • Component/s: security-libs
    • None

      When the specified transformation string contains 3 or more slashes, e.g. AES/GCM//, the existing code in the javax.crypto.Cipher class breaks it into 3 components by lumping all input trailing the 2nd slash as padding scheme.
      Instead of passing "/" as the padding scheme which leads to NoSuchPaddingException, the expected behavior is to throw NoSuchAlgorithmException.

            Assignee:
            Unassigned
            Reporter:
            Valerie Peng
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: