From 70f2e3e20ff7dd10d2b405764f4818b11f167925 Mon Sep 17 00:00:00 2001
From: Tom Lane
Date: Tue, 19 May 2015 18:33:58 -0400
Subject: Last-minute updates for release notes.
Revise description of CVE-2015-3166, in line with scaled-back patch.
Change release date.
Security: CVE-2015-3166
---
doc/src/sgml/release-9.0.sgml | 26 ++++++++++++++++----------
doc/src/sgml/release-9.1.sgml | 26 ++++++++++++++++----------
doc/src/sgml/release-9.2.sgml | 26 ++++++++++++++++----------
doc/src/sgml/release-9.3.sgml | 26 ++++++++++++++++----------
4 files changed, 64 insertions(+), 40 deletions(-)
diff --git a/doc/src/sgml/release-9.0.sgml b/doc/src/sgml/release-9.0.sgml
index a3d9461fa6f..9794b5b3b76 100644
--- a/doc/src/sgml/release-9.0.sgml
+++ b/doc/src/sgml/release-9.0.sgml
@@ -6,7 +6,7 @@
Release Date
- 2015-05-21
+ 2015-05-22
@@ -58,18 +58,24 @@
- Consistently check for failure of the *printf() family of
- functions (Noah Misch)
+ Improve detection of system-call failures (Noah Misch)
- Most calls of these functions did not consider the possibility that
- the functions could fail with, eg, out-of-memory conditions. The usual
- result would just be missing output, but crashes or exposure of
- unintended information are also possible. To protect against such
- risks uniformly, create wrappers around these functions that throw an
- error on failure. Also add missing error checks to a few
- security-relevant calls of other system functions.
+ Our replacement implementation of snprintf() failed to
+ check for errors reported by the underlying system library calls;
+ the main case that might be missed is out-of-memory situations.
+ In the worst case this might lead to information exposure, due to our
+ code assuming that a buffer had been overwritten when it hadn't been.
+ Also, there were a few places in which security-relevant calls of other
+ system library functions did not check for failure.
+
+
+
+ It remains possible that some calls of the *printf()
+ family of functions are vulnerable to information disclosure if an
+ out-of-memory error occurs at just the wrong time. We judge the risk
+ to not be large, but will continue analysis in this area.
(CVE-2015-3166)
diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml
index 82dde5e038b..f6c0d131576 100644
--- a/doc/src/sgml/release-9.1.sgml
+++ b/doc/src/sgml/release-9.1.sgml
@@ -6,7 +6,7 @@
Release Date
- 2015-05-21
+ 2015-05-22
@@ -58,18 +58,24 @@
- Consistently check for failure of the *printf() family of
- functions (Noah Misch)
+ Improve detection of system-call failures (Noah Misch)
- Most calls of these functions did not consider the possibility that
- the functions could fail with, eg, out-of-memory conditions. The usual
- result would just be missing output, but crashes or exposure of
- unintended information are also possible. To protect against such
- risks uniformly, create wrappers around these functions that throw an
- error on failure. Also add missing error checks to a few
- security-relevant calls of other system functions.
+ Our replacement implementation of snprintf() failed to
+ check for errors reported by the underlying system library calls;
+ the main case that might be missed is out-of-memory situations.
+ In the worst case this might lead to information exposure, due to our
+ code assuming that a buffer had been overwritten when it hadn't been.
+ Also, there were a few places in which security-relevant calls of other
+ system library functions did not check for failure.
+
+
+
+ It remains possible that some calls of the *printf()
+ family of functions are vulnerable to information disclosure if an
+ out-of-memory error occurs at just the wrong time. We judge the risk
+ to not be large, but will continue analysis in this area.
(CVE-2015-3166)
diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml
index ff715efaa59..168a387d345 100644
--- a/doc/src/sgml/release-9.2.sgml
+++ b/doc/src/sgml/release-9.2.sgml
@@ -6,7 +6,7 @@
Release Date
- 2015-05-21
+ 2015-05-22
@@ -58,18 +58,24 @@
- Consistently check for failure of the *printf() family of
- functions (Noah Misch)
+ Improve detection of system-call failures (Noah Misch)
- Most calls of these functions did not consider the possibility that
- the functions could fail with, eg, out-of-memory conditions. The usual
- result would just be missing output, but crashes or exposure of
- unintended information are also possible. To protect against such
- risks uniformly, create wrappers around these functions that throw an
- error on failure. Also add missing error checks to a few
- security-relevant calls of other system functions.
+ Our replacement implementation of snprintf() failed to
+ check for errors reported by the underlying system library calls;
+ the main case that might be missed is out-of-memory situations.
+ In the worst case this might lead to information exposure, due to our
+ code assuming that a buffer had been overwritten when it hadn't been.
+ Also, there were a few places in which security-relevant calls of other
+ system library functions did not check for failure.
+
+
+
+ It remains possible that some calls of the *printf()
+ family of functions are vulnerable to information disclosure if an
+ out-of-memory error occurs at just the wrong time. We judge the risk
+ to not be large, but will continue analysis in this area.
(CVE-2015-3166)
diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml
index 4c0d8535435..38f3354bd8f 100644
--- a/doc/src/sgml/release-9.3.sgml
+++ b/doc/src/sgml/release-9.3.sgml
@@ -6,7 +6,7 @@
Release Date
- 2015-05-21
+ 2015-05-22
@@ -58,18 +58,24 @@
- Consistently check for failure of the *printf() family of
- functions (Noah Misch)
+ Improve detection of system-call failures (Noah Misch)
- Most calls of these functions did not consider the possibility that
- the functions could fail with, eg, out-of-memory conditions. The usual
- result would just be missing output, but crashes or exposure of
- unintended information are also possible. To protect against such
- risks uniformly, create wrappers around these functions that throw an
- error on failure. Also add missing error checks to a few
- security-relevant calls of other system functions.
+ Our replacement implementation of snprintf() failed to
+ check for errors reported by the underlying system library calls;
+ the main case that might be missed is out-of-memory situations.
+ In the worst case this might lead to information exposure, due to our
+ code assuming that a buffer had been overwritten when it hadn't been.
+ Also, there were a few places in which security-relevant calls of other
+ system library functions did not check for failure.
+
+
+
+ It remains possible that some calls of the *printf()
+ family of functions are vulnerable to information disclosure if an
+ out-of-memory error occurs at just the wrong time. We judge the risk
+ to not be large, but will continue analysis in this area.
(CVE-2015-3166)
--
cgit v1.2.3