database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-27 12:41:57 +03:00
Code Activity

pgcrypto: Report errant decryption as "Wrong key or corrupt data".

Browse Source 
This has been the predominant outcome.  When the output of decrypting
with a wrong key coincidentally resembled an OpenPGP packet header,
pgcrypto could instead report "Corrupt data", "Not text data" or
"Unsupported compression algorithm".  The distinct "Corrupt data"
message added no value.  The latter two error messages misled when the
decrypted payload also exhibited fundamental integrity problems.  Worse,
error message variance in other systems has enabled cryptologic attacks;
see RFC 4880 section "14. Security Considerations".  Whether these
pgcrypto behaviors are likewise exploitable is unknown.

In passing, document that pgcrypto does not resist side-channel attacks.
Back-patch to 9.0 (all supported versions).

Security: CVE-2015-3167
This commit is contained in:
Noah Misch
2015-05-18 10:02:31 -04:00
parent c669915fd9
commit 7b758b7d60
9 changed files with 162 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/pgcrypto.sgml
View File

@ -1224,6 +1224,14 @@ gen_random_bytes(count integer) returns bytea
<para>
If you cannot, then better do crypto inside client application.
</para>
<para>
The implementation does not resist
<ulink url="http://en.wikipedia.org/wiki/Side-channel_attack">side-channel
attacks</ulink>. For example, the time required for
a <filename>pgcrypto</> decryption function to complete varies among
ciphertexts of a given size.
</para>
</sect3>
<sect3>