Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit19d47ed

Browse files
committed
Last-minute updates for release notes.
Add entries for security issues.Security:CVE-2015-3165 throughCVE-2015-3167
1 parent85270ac commit19d47ed

File tree

5 files changed

+299
-0
lines changed

5 files changed

+299
-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

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

Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,101 @@
3939

4040
<itemizedlist>
4141

42+
<!--
43+
Author: Noah Misch <noah@leadboat.com>
44+
Branch: master [b0ce38503] 2015-05-18 10:02:31 -0400
45+
Branch: REL9_4_STABLE [7a0d48ac7] 2015-05-18 10:02:35 -0400
46+
Branch: REL9_3_STABLE [f4c12b415] 2015-05-18 10:02:36 -0400
47+
Branch: REL9_2_STABLE [439ff9b6b] 2015-05-18 10:02:37 -0400
48+
Branch: REL9_1_STABLE [6675ab595] 2015-05-18 10:02:38 -0400
49+
Branch: REL9_0_STABLE [648e41a6e] 2015-05-18 10:02:38 -0400
50+
-->
51+
52+
<listitem>
53+
<para>
54+
Avoid possible crash when client disconnects just before the
55+
authentication timeout expires (Benkocs Norbert Attila)
56+
</para>
57+
58+
<para>
59+
If the timeout interrupt fired partway through the session shutdown
60+
sequence, SSL-related state would be freed twice, typically causing a
61+
crash and hence denial of service to other sessions. Experimentation
62+
shows that an unauthenticated remote attacker could trigger the bug
63+
somewhat consistently, hence treat as security issue.
64+
(CVE-2015-3165)
65+
</para>
66+
</listitem>
67+
68+
<!--
69+
Author: Noah Misch <noah@leadboat.com>
70+
Branch: master [cac18a76b] 2015-05-18 10:02:31 -0400
71+
Branch: REL9_4_STABLE [f7c4fe7d9] 2015-05-18 10:02:35 -0400
72+
Branch: REL9_3_STABLE [d5abbd114] 2015-05-18 10:02:36 -0400
73+
Branch: REL9_2_STABLE [1e6652aea] 2015-05-18 10:02:37 -0400
74+
Branch: REL9_1_STABLE [b544dcdad] 2015-05-18 10:02:38 -0400
75+
Branch: REL9_0_STABLE [19f7adc01] 2015-05-18 10:02:38 -0400
76+
Author: Noah Misch <noah@leadboat.com>
77+
Branch: master [16304a013] 2015-05-18 10:02:31 -0400
78+
Branch: REL9_4_STABLE [2e3bd0665] 2015-05-18 10:02:35 -0400
79+
Branch: REL9_3_STABLE [34d21e770] 2015-05-18 10:02:36 -0400
80+
Branch: REL9_2_STABLE [82b7393eb] 2015-05-18 10:02:37 -0400
81+
Branch: REL9_1_STABLE [e58f042d9] 2015-05-18 10:02:38 -0400
82+
Branch: REL9_0_STABLE [b08c7aff7] 2015-05-18 10:02:38 -0400
83+
Author: Noah Misch <noah@leadboat.com>
84+
Branch: master [fd97bd411] 2015-05-18 10:02:31 -0400
85+
Branch: REL9_4_STABLE [ca325941d] 2015-05-18 10:02:35 -0400
86+
Branch: REL9_3_STABLE [c669915fd] 2015-05-18 10:02:37 -0400
87+
Branch: REL9_2_STABLE [01272d95a] 2015-05-18 10:02:37 -0400
88+
Branch: REL9_1_STABLE [2cb9f2cab] 2015-05-18 10:02:38 -0400
89+
Branch: REL9_0_STABLE [9b5e831e3] 2015-05-18 10:02:38 -0400
90+
-->
91+
92+
<listitem>
93+
<para>
94+
Consistently check for failure of the <function>*printf()</> family of
95+
functions (Noah Misch)
96+
</para>
97+
98+
<para>
99+
Most calls of these functions did not consider the possibility that
100+
the functions could fail with, eg, out-of-memory conditions. The usual
101+
result would just be missing output, but crashes or exposure of
102+
unintended information are also possible. To protect against such
103+
risks uniformly, create wrappers around these functions that throw an
104+
error on failure. Also add missing error checks to a few
105+
security-relevant calls of other system functions.
106+
(CVE-2015-3166)
107+
</para>
108+
</listitem>
109+
110+
<!--
111+
Author: Noah Misch <noah@leadboat.com>
112+
Branch: master [85270ac7a] 2015-05-18 10:02:31 -0400
113+
Branch: REL9_4_STABLE [fba1fb4ef] 2015-05-18 10:02:35 -0400
114+
Branch: REL9_3_STABLE [7b758b7d6] 2015-05-18 10:02:37 -0400
115+
Branch: REL9_2_STABLE [0ba200431] 2015-05-18 10:02:37 -0400
116+
Branch: REL9_1_STABLE [e5981aebd] 2015-05-18 10:02:38 -0400
117+
Branch: REL9_0_STABLE [b84e5c017] 2015-05-18 10:02:39 -0400
118+
-->
119+
120+
<listitem>
121+
<para>
122+
In <filename>contrib/pgcrypto</>, uniformly report decryption failures
123+
as <quote>Wrong key or corrupt data</> (Noah Misch)
124+
</para>
125+
126+
<para>
127+
Previously, some cases of decryption with an incorrect key could report
128+
other error message texts. It has been shown that such variance in
129+
error reports can aid attackers in recovering keys from other systems.
130+
While it's unknown whether <filename>pgcrypto</>'s specific behaviors
131+
are likewise exploitable, it seems better to avoid the risk by using a
132+
one-size-fits-all message.
133+
(CVE-2015-3167)
134+
</para>
135+
</listitem>
136+
42137
<!--
43138
Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
44139
Branch: master [b69bf30b9] 2015-04-28 11:32:53 -0300

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp