Impact

Vulnerability in SecureProps involves a regex failing to detect tags during decryption of encrypted data.

This occurs when the encrypted data has been encoded with NullEncoder and passed to TagAwareCipher, and contains special characters such as \n. As a result, the decryption process is skipped since the tags are not detected. This causes the encrypted data to be returned in plain format.

The vulnerability affects users who implement TagAwareCipher with any base cipher that has NullEncoder (not default).

Patches

The patch for the issue has been released. Users are advised to update to version 1.2.2.

Workarounds

The main recommendation is to update to the latest version as there are no breaking changes.

If that's not possible, you can use the default Base64Encoder with the base cipher decorated with TagAwareCipher to prevent special characters in the encrypted string from interfering with regex tag detection logic.

This workaround is safe but may involve double encoding since TagAwareCipher uses Base64Encoder by default.

References

Reported issue: IlicMiljan/Secure-Props#20
Pull request resolving bug: IlicMiljan/Secure-Props#21

References

• GHSA-rj29-j2g4-77q8
• IlicMiljan/Secure-Props#20
• IlicMiljan/Secure-Props#21
• IlicMiljan/Secure-Props@ab7b561
• https://nvd.nist.gov/vuln/detail/CVE-2024-28864