Text encryption using AES 128-bit or AES 256-bit targeting fields where there is a colon ":" on the 33rd character seems to break the process. 

Testing with other combinations, such as those listed below, the issue is not observed: 

testing testing : testing
testing testing testing : testing
testing testing testing testing testing : testing

When performing a 'Mass Encryption' from the Encrypted Field Configuration record, if you navigate to the task table and search for that record, the description field shows fine. It still does not show on the problem list or form.

Steps to Reproduce

1. Activate the "Encryption Support" plugin.

2. Navigate to System Security > Encryption Contexts .

3. Create a new Encryption Context using the type "AES 128-bit" or "AES 256-bit".

4. Navigate to User Administration > Roles .

5. Add the 'Encryption context' field to the form.

6. Assign this new Encryption Context to the 'admin' role.

7. Log out and log back in as the 'System Administrator' user and elevate your 'Security_admin' privileges. This should ensure you receive the Encryption context and be able to access the application.

8. Navigate to Problem > All .

9. Personalise the list and add the 'Description' column to the list.

10. Open any record and modify the value of the 'Description' field to be the following:
testing testing testing testing : testing

11. Navigate to System Security > Encrypted Field Configurations .

12. Create a new 'Encrypted Field Configuration' record with the following fields value:
Table = Problem
Method = Single Encryption Context
Column = Description
Encryption context = (Record we created in step 2)

13. Navigate to the problem list again and find the record modified in step 10.

Observe the description value is blank on the list, and when opening the record, the description field does not appear.


This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article.

The workaround is to edit the target records to have the colon character shifted one space. A before-insert Business Rule can also be created to ensure that these fields do not have the colon character ':' at the 33rd position.

Related Problem: PRB1316691

Seen In

SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - VR - Rapid7 - London 2019 Q2 v.6.2.1
SR - VR - Vulnerability Response - New York 2019 Q3

Fixed In


Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-07-07 20:09:51