lp:ubuntu/vivid-security/postgresql-9.4
- Get this branch:
- bzr branch lp:ubuntu/vivid-security/postgresql-9.4
Branch merges
Related source package recipes
Branch information
Recent revisions
- 13. By Martin Pitt
-
* New upstream security/bug fix release: (LP: #1504132)
- Guard against stack overflows in json parsing.
If an application constructs PostgreSQL json or jsonb values from
arbitrary user input, the application's users can reliably crash the
PostgreSQL server, causing momentary denial of service. (CVE-2015-5289)- Fix contrib/pgcrypto to detect and report too-short crypt() salts
Certain invalid salt arguments crashed the server or disclosed a few
bytes of server memory. We have not ruled out the viability of attacks
that arrange for presence of confidential information in the disclosed
bytes, but they seem unlikely. (CVE-2015-5288)- See release notes for details about other fixes.
- 12. By Martin Pitt
-
* New upstream security/bug fix release (LP: #1457093)
- Avoid possible crash when client disconnects just before the
authentication timeout expires.
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
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
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
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.- See release notes for details about other fixes.
- 11. By Christoph Berg
-
* New upstream version.
+ libpq5: Name lookups fixed in minimal chroots (Closes: #756627)
+ Fix buffer overruns in to_char() (CVE-2015-0241)
+ Fix buffer overruns in contrib/pgcrypto (CVE-2015-0243)
+ Fix possible loss of frontend/backend protocol synchronization after an
error (CVE-2015-0244)
+ Fix information leak via constraint-violation error messages
(CVE-2014-8161) - 9. By Christoph Berg
-
* First 9.4 RC release.
* Update psql call in dump-reload instructions.
* Reenable 010_pg_basebackup.t tests, fixed upstream. - 7. By Christoph Berg
-
* postgresql-
9.4.preinst: Output detailed dump-reload instructions when
refusing the package upgrade, and also add a NEWS item about it.
(Closes: #764705)
* Add libipc-run-perl for the regression tests which otherwise skip large
parts.
* Update Standards-Version. - 6. By Christoph Berg
-
* New upstream beta version.
+ Catalog version number changed, older 9.4 clusters need to be dumped and
reloaded.
+ Regexp regression fixed. (Closes: #760564)
+ CACHE_LINE_SIZE definition renamed to mitigate conflict on *BSD.
(Closes: #763098)[ Martin Pitt ]
* Add missing logrotate test dependency.[ Christoph Berg ]
* Set Multi-Arch: foreign in postgresql-client- 9.4 and postgresql-doc-9.4.
(Closes: #757520; do it even on non-multiarch dists, it doesn't hurt.)
* Fix postgresql_fdw in description, spotted by Andrei Popescu, thanks!
(Closes: #762389) - 4. By Christoph Berg
-
* New upstream beta version.
+ Secure Unix-domain sockets of temporary postmasters started during make
check (Noah Misch)Any local user able to access the socket file could connect as the
server's bootstrap superuser, then proceed to execute arbitrary code as
the operating-system user running the test, as we previously noted in
CVE-2014-0067. This change defends against that risk by placing the
server's socket in a temporary, mode 0700 subdirectory of /tmp.* postgresql-
9.4.preinst: Fail upgrade when upgrading from beta1, the
catalog version changed. People should dump/remove their old clusters
first.
* Use util-linux' uuid lib as backend for the uuid-ossp extension
(--with-uuid=e2fs) .
* Enable sepgsql (--with-selinux). On systems with libselinux1-dev < 2.1.10,
this is automatically disabled.
* Revert multiarch for libpq-dev and libecpg-dev. (Closes: #750111, #750112)
* Remove our pg_regress patches to support --host=/path. Implemented
upstream as fix for CVE-2014-0067.
* debian/copyright: Say that there are various copyright holders for the
contrib modules. (Hello Lintian!)
* Update Vcs URLs.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:ubuntu/wily/postgresql-9.4
