Lookups: fix pgsql multiple-row, single-column return

[exim.git] / doc / doc-txt / ChangeLog

diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 0ea49a280132de83a34d923389ad0c31deea3a03..08ed2ce9d1b262a15b47e8f0d138a692c9f98881 100644 (file)
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -5,6 +5,13 @@ affect Exim's operation, with an unchanged configuration file.  For new
 options, and new features, see the NewStuff file next to this ChangeLog.
 
 
+Since Exim version 4.90
+-----------------
+
+JH/03 Fix pgsql lookup for multiple result-tuples with a single column.
+      Previously only the last row was returned.
+
+
 Exim version 4.90
 -----------------
 
@@ -195,7 +202,16 @@ JH/33 Downgrade an unfound-list name (usually a typo in the config file) from
 
 JH/34 Bug 2199: Fix a use-after-free while reading smtp input for header lines.
       A crafted sequence of BDAT commands could result in in-use memory beeing
-      freed.
+      freed.  CVE-2017-16943.
+
+HS/03 Bug 2201: Fix checking for leading-dot on a line during headers reading
+      from SMTP input.  Previously it was always done; now only done for DATA
+      and not BDAT commands.  CVE-2017-16944.
+
+JH/35 Bug 2201: Flush received data in BDAT mode after detecting an error fatal
+      to the message (such as an overlong header line).  Previously this was
+      not done and we did not exit BDAT mode.  Followon from the previous item
+      though a different problem.
 
 
 Exim version 4.89