postgres is using deprecated /proc/PID/oom_adj

Bug #991725 reported by Uqbar on 2012-04-30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
postgresql-9.3 (Debian)
Fix Released
postgresql-9.3 (Ubuntu)

Bug Description

From my syslogs I get the following:

postgres (1358): /proc/1358/oom_adj is deprecated, please use /proc/1358/oom_score_adj instead

That should be fixed either upstream or in Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: postgresql 9.1+129
ProcVersionSignature: Ubuntu 3.2.0-23.31-lowlatency-pae 3.2.14
Uname: Linux 3.2.0-23-lowlatency-pae i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Mon Apr 30 09:17:29 2012
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
PackageArchitecture: all
SourcePackage: postgresql-common
UpgradeStatus: Upgraded to precise on 2012-04-27 (3 days ago)

Uqbar (uqbar) wrote :
Martin Pitt (pitti) on 2012-08-24
affects: postgresql-common (Ubuntu) → postgresql-9.1 (Ubuntu)
Changed in postgresql-9.1 (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Changed in postgresql-9.1 (Debian):
status: Unknown → New
Changed in postgresql-9.1 (Debian):
status: New → Confirmed
Martin Pitt (pitti) on 2014-01-07
affects: postgresql-9.1 (Ubuntu) → postgresql-9.3 (Ubuntu)
Martin Pitt (pitti) on 2014-01-07
affects: postgresql-9.1 (Debian) → postgresql-9.3 (Debian)
Martin Pitt (pitti) wrote :

Fixed in packaging bzr.

Changed in postgresql-9.3 (Ubuntu):
status: Triaged → Fix Committed
Changed in postgresql-9.3 (Debian):
status: Confirmed → Fix Committed
Launchpad Janitor (janitor) wrote :
Download full text (5.8 KiB)

This bug was fixed in the package postgresql-9.3 - 9.3.3-1

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

  [ Christoph Berg ]
  * New upstream security/bugfix release.

    + Shore up GRANT ... WITH ADMIN OPTION restrictions (Noah Misch)

      Granting a role without ADMIN OPTION is supposed to prevent the grantee
      from adding or removing members from the granted role, but this
      restriction was easily bypassed by doing SET ROLE first. The security
      impact is mostly that a role member can revoke the access of others,
      contrary to the wishes of his grantor. Unapproved role member additions
      are a lesser concern, since an uncooperative role member could provide
      most of his rights to others anyway by creating views or SECURITY
      DEFINER functions. (CVE-2014-0060)

    + Prevent privilege escalation via manual calls to PL validator functions
      (Andres Freund)

      The primary role of PL validator functions is to be called implicitly
      during CREATE FUNCTION, but they are also normal SQL functions that a
      user can call explicitly. Calling a validator on a function actually
      written in some other language was not checked for and could be
      exploited for privilege-escalation purposes. The fix involves adding a
      call to a privilege-checking function in each validator function.
      Non-core procedural languages will also need to make this change to
      their own validator functions, if any. (CVE-2014-0061)

    + Avoid multiple name lookups during table and index DDL (Robert Haas,
      Andres Freund)

      If the name lookups come to different conclusions due to concurrent
      activity, we might perform some parts of the DDL on a different table
      than other parts. At least in the case of CREATE INDEX, this can be used
      to cause the permissions checks to be performed against a different
      table than the index creation, allowing for a privilege escalation
      attack. (CVE-2014-0062)

    + Prevent buffer overrun with long datetime strings (Noah Misch)

      The MAXDATELEN constant was too small for the longest possible value of
      type interval, allowing a buffer overrun in interval_out(). Although the
      datetime input functions were more careful about avoiding buffer
      overrun, the limit was short enough to cause them to reject some valid
      inputs, such as input containing a very long timezone name. The ecpg
      library contained these vulnerabilities along with some of its own.

    + Prevent buffer overrun due to integer overflow in size calculations
      (Noah Misch, Heikki Linnakangas)

      Several functions, mostly type input functions, calculated an allocation
      size without checking for overflow. If overflow did occur, a too-small
      buffer would be allocated and then written past. (CVE-2014-0064)

    + Prevent overruns of fixed-size buffers (Peter Eisentraut, Jozef Mlich)

      Use strlcpy() and related functions to provide a clear guarantee that
      fixed-size buffers are not overrun. Unlike the preceding items, it is
      unclear whether these cases really represent live issues, ...


Changed in postgresql-9.3 (Ubuntu):
status: Fix Committed → Fix Released
Changed in postgresql-9.3 (Debian):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.