The snprintf implementation in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7, and 9.4.x before 9.4.2 does not properly handle system-call errors, which allows attackers to obtain sensitive information or have other unspecified impact via unknown vectors, as demonstrated by an out-of-memory error.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Link | Tags |
---|---|
http://www.postgresql.org/about/news/1587/ | vendor advisory |
http://www.postgresql.org/docs/9.0/static/release-9-0-20.html | release notes vendor advisory |
http://www.postgresql.org/docs/9.1/static/release-9-1-16.html | release notes vendor advisory |
http://www.postgresql.org/docs/9.2/static/release-9-2-11.html | release notes vendor advisory |
http://www.postgresql.org/docs/9.3/static/release-9-3-7.html | release notes vendor advisory |
http://www.postgresql.org/docs/9.4/static/release-9-4-2.html | release notes vendor advisory |
http://www.debian.org/security/2015/dsa-3269 | third party advisory |
http://www.debian.org/security/2015/dsa-3270 | third party advisory |
http://ubuntu.com/usn/usn-2621-1 | third party advisory |