Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 32f8d57

Browse files
tglsfdctglsfdc
committed
Last-minute updates for release notes.
Add entries for security issues. Security: CVE-2015-3165 through CVE-2015-3167
1 parent 7b758b7 commit 32f8d57

File tree

4 files changed

+204
-0
lines changed

4 files changed

+204
-0
lines changed

‎doc/src/sgml/release-9.0.sgml

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,57 @@
4040

4141
<itemizedlist>
4242

43+
<listitem>
44+
<para>
45+
Avoid possible crash when client disconnects just before the
46+
authentication timeout expires (Benkocs Norbert Attila)
47+
</para>
48+
49+
<para>
50+
If the timeout interrupt fired partway through the session shutdown
51+
sequence, SSL-related state would be freed twice, typically causing a
52+
crash and hence denial of service to other sessions. Experimentation
53+
shows that an unauthenticated remote attacker could trigger the bug
54+
somewhat consistently, hence treat as security issue.
55+
(CVE-2015-3165)
56+
</para>
57+
</listitem>
58+
59+
<listitem>
60+
<para>
61+
Consistently check for failure of the <function>*printf()</> family of
62+
functions (Noah Misch)
63+
</para>
64+
65+
<para>
66+
Most calls of these functions did not consider the possibility that
67+
the functions could fail with, eg, out-of-memory conditions. The usual
68+
result would just be missing output, but crashes or exposure of
69+
unintended information are also possible. To protect against such
70+
risks uniformly, create wrappers around these functions that throw an
71+
error on failure. Also add missing error checks to a few
72+
security-relevant calls of other system functions.
73+
(CVE-2015-3166)
74+
</para>
75+
</listitem>
76+
77+
<listitem>
78+
<para>
79+
In <filename>contrib/pgcrypto</>, uniformly report decryption failures
80+
as <quote>Wrong key or corrupt data</> (Noah Misch)
81+
</para>
82+
83+
<para>
84+
Previously, some cases of decryption with an incorrect key could report
85+
other error message texts. It has been shown that such variance in
86+
error reports can aid attackers in recovering keys from other systems.
87+
While it's unknown whether <filename>pgcrypto</>'s specific behaviors
88+
are likewise exploitable, it seems better to avoid the risk by using a
89+
one-size-fits-all message.
90+
(CVE-2015-3167)
91+
</para>
92+
</listitem>
93+
4394
<listitem>
4495
<para>
4596
Fix incorrect checking of deferred exclusion constraints after a HOT

‎doc/src/sgml/release-9.1.sgml

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,57 @@
4040

4141
<itemizedlist>
4242

43+
<listitem>
44+
<para>
45+
Avoid possible crash when client disconnects just before the
46+
authentication timeout expires (Benkocs Norbert Attila)
47+
</para>
48+
49+
<para>
50+
If the timeout interrupt fired partway through the session shutdown
51+
sequence, SSL-related state would be freed twice, typically causing a
52+
crash and hence denial of service to other sessions. Experimentation
53+
shows that an unauthenticated remote attacker could trigger the bug
54+
somewhat consistently, hence treat as security issue.
55+
(CVE-2015-3165)
56+
</para>
57+
</listitem>
58+
59+
<listitem>
60+
<para>
61+
Consistently check for failure of the <function>*printf()</> family of
62+
functions (Noah Misch)
63+
</para>
64+
65+
<para>
66+
Most calls of these functions did not consider the possibility that
67+
the functions could fail with, eg, out-of-memory conditions. The usual
68+
result would just be missing output, but crashes or exposure of
69+
unintended information are also possible. To protect against such
70+
risks uniformly, create wrappers around these functions that throw an
71+
error on failure. Also add missing error checks to a few
72+
security-relevant calls of other system functions.
73+
(CVE-2015-3166)
74+
</para>
75+
</listitem>
76+
77+
<listitem>
78+
<para>
79+
In <filename>contrib/pgcrypto</>, uniformly report decryption failures
80+
as <quote>Wrong key or corrupt data</> (Noah Misch)
81+
</para>
82+
83+
<para>
84+
Previously, some cases of decryption with an incorrect key could report
85+
other error message texts. It has been shown that such variance in
86+
error reports can aid attackers in recovering keys from other systems.
87+
While it's unknown whether <filename>pgcrypto</>'s specific behaviors
88+
are likewise exploitable, it seems better to avoid the risk by using a
89+
one-size-fits-all message.
90+
(CVE-2015-3167)
91+
</para>
92+
</listitem>
93+
4394
<listitem>
4495
<para>
4596
Fix incorrect declaration of <filename>contrib/citext</>'s

‎doc/src/sgml/release-9.2.sgml

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,57 @@
4040

4141
<itemizedlist>
4242

43+
<listitem>
44+
<para>
45+
Avoid possible crash when client disconnects just before the
46+
authentication timeout expires (Benkocs Norbert Attila)
47+
</para>
48+
49+
<para>
50+
If the timeout interrupt fired partway through the session shutdown
51+
sequence, SSL-related state would be freed twice, typically causing a
52+
crash and hence denial of service to other sessions. Experimentation
53+
shows that an unauthenticated remote attacker could trigger the bug
54+
somewhat consistently, hence treat as security issue.
55+
(CVE-2015-3165)
56+
</para>
57+
</listitem>
58+
59+
<listitem>
60+
<para>
61+
Consistently check for failure of the <function>*printf()</> family of
62+
functions (Noah Misch)
63+
</para>
64+
65+
<para>
66+
Most calls of these functions did not consider the possibility that
67+
the functions could fail with, eg, out-of-memory conditions. The usual
68+
result would just be missing output, but crashes or exposure of
69+
unintended information are also possible. To protect against such
70+
risks uniformly, create wrappers around these functions that throw an
71+
error on failure. Also add missing error checks to a few
72+
security-relevant calls of other system functions.
73+
(CVE-2015-3166)
74+
</para>
75+
</listitem>
76+
77+
<listitem>
78+
<para>
79+
In <filename>contrib/pgcrypto</>, uniformly report decryption failures
80+
as <quote>Wrong key or corrupt data</> (Noah Misch)
81+
</para>
82+
83+
<para>
84+
Previously, some cases of decryption with an incorrect key could report
85+
other error message texts. It has been shown that such variance in
86+
error reports can aid attackers in recovering keys from other systems.
87+
While it's unknown whether <filename>pgcrypto</>'s specific behaviors
88+
are likewise exploitable, it seems better to avoid the risk by using a
89+
one-size-fits-all message.
90+
(CVE-2015-3167)
91+
</para>
92+
</listitem>
93+
4394
<listitem>
4495
<para>
4596
Fix incorrect declaration of <filename>contrib/citext</>'s

‎doc/src/sgml/release-9.3.sgml

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,57 @@
4040

4141
<itemizedlist>
4242

43+
<listitem>
44+
<para>
45+
Avoid possible crash when client disconnects just before the
46+
authentication timeout expires (Benkocs Norbert Attila)
47+
</para>
48+
49+
<para>
50+
If the timeout interrupt fired partway through the session shutdown
51+
sequence, SSL-related state would be freed twice, typically causing a
52+
crash and hence denial of service to other sessions. Experimentation
53+
shows that an unauthenticated remote attacker could trigger the bug
54+
somewhat consistently, hence treat as security issue.
55+
(CVE-2015-3165)
56+
</para>
57+
</listitem>
58+
59+
<listitem>
60+
<para>
61+
Consistently check for failure of the <function>*printf()</> family of
62+
functions (Noah Misch)
63+
</para>
64+
65+
<para>
66+
Most calls of these functions did not consider the possibility that
67+
the functions could fail with, eg, out-of-memory conditions. The usual
68+
result would just be missing output, but crashes or exposure of
69+
unintended information are also possible. To protect against such
70+
risks uniformly, create wrappers around these functions that throw an
71+
error on failure. Also add missing error checks to a few
72+
security-relevant calls of other system functions.
73+
(CVE-2015-3166)
74+
</para>
75+
</listitem>
76+
77+
<listitem>
78+
<para>
79+
In <filename>contrib/pgcrypto</>, uniformly report decryption failures
80+
as <quote>Wrong key or corrupt data</> (Noah Misch)
81+
</para>
82+
83+
<para>
84+
Previously, some cases of decryption with an incorrect key could report
85+
other error message texts. It has been shown that such variance in
86+
error reports can aid attackers in recovering keys from other systems.
87+
While it's unknown whether <filename>pgcrypto</>'s specific behaviors
88+
are likewise exploitable, it seems better to avoid the risk by using a
89+
one-size-fits-all message.
90+
(CVE-2015-3167)
91+
</para>
92+
</listitem>
93+
4394
<listitem>
4495
<para>
4596
Protect against wraparound of multixact member IDs

0 commit comments

Comments
 (0)