Quick Links

postgresql-9.3 updated to version 9.3.7-1.pgdg+1

From:	apt(dot)postgresql(dot)org repository <myon(at)debian(dot)org>
To:	PostgreSQL in Debian <pgsql-pkg-debian(at)postgresql(dot)org>
Subject:	postgresql-9.3 updated to version 9.3.7-1.pgdg+1
Date:	2015-05-22 12:58:49
Message-ID:	E1YvmXJ-00007O-Uh@atalia.postgresql.org
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-pkg-debian

The package postgresql-9.3 was updated on apt.postgresql.org:

New version 9.3.7-1.pgdg+1:

Old version 9.3.6-1.pgdg+1:

Changelog:

postgresql-9.3 (9.3.7-1.pgdg+1) sid-pgdg; urgency=low

* Rebuild for sid-pgdg (jenkins-postgresql-9.3-source-
distribution=sid-209, git revision
0535d15814bcbe2eb675fc956cca06c55534d635)

-- apt.postgresql.org autobuilder <myon(at)debian(dot)org> Wed, 20 May 2015 13:34:05 +0200

postgresql-9.3 (9.3.7-1) unstable; urgency=medium

* New upstream version.

+ Avoid possible crash when client disconnects just before the
authentication timeout expires (Benkocs Norbert Attila)

If the timeout interrupt fired partway through the session shutdown
sequence, SSL-related state would be freed twice, typically causing a
crash and hence denial of service to other sessions. Experimentation
shows that an unauthenticated remote attacker could trigger the bug
somewhat consistently, hence treat as security issue. (CVE-2015-3165)

+ Improve detection of system-call failures (Noah Misch)

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)

+ In contrib/pgcrypto, uniformly report decryption failures as Wrong key
or corrupt data (Noah Misch)

Previously, some cases of decryption with an incorrect key could report
other error message texts. It has been shown that such variance in
error reports can aid attackers in recovering keys from other systems.
While it's unknown whether pgcrypto's specific behaviors are likewise
exploitable, it seems better to avoid the risk by using a
one-size-fits-all message. (CVE-2015-3167)

+ Protect against wraparound of multixact member IDs
(lvaro Herrera, Robert Haas, Thomas Munro)

Under certain usage patterns, the existing defenses against this might
be insufficient, allowing pg_multixact/members files to be removed too
early, resulting in data loss.
The fix for this includes modifying the server to fail transactions that
would result in overwriting old multixact member ID data, and improving
autovacuum to ensure it will act proactively to prevent multixact member
ID wraparound, as it does for transaction ID wraparound.

* Repository moved to git, update Vcs headers.

-- Christoph Berg <christoph(dot)berg(at)credativ(dot)de> Wed, 20 May 2015 13:31:31 +0200

The public mirrors serving apt.postgresql.org are synced hourly,
the updated packages will be available there shortly.

Browse pgsql-pkg-debian by date

	From	Date	Subject
Next Message	apt.postgresql.org repository	2015-05-22 12:59:03	postgresql-9.2 updated to version 9.2.11-1.pgdg+1
Previous Message	apt.postgresql.org repository	2015-05-22 12:58:25	postgresql-9.4 updated to version 9.4.2-1.pgdg+1