Improper validation of type oidvector in PostgreSQL
allows a database user to disclose a few bytes of server
memory. We have not ruled out viability of attacks that
arrange for presence of confidential information in
disclosed bytes, but they seem unlikely.
Missing validation of type of input in PostgreSQL
intarray extension selectivity estimator function allows
an object creator to execute arbitrary code as the
operating system user running the database.
Heap buffer overflow in PostgreSQL pgcrypto allows a
ciphertext provider to execute arbitrary code as the
operating system user running the database.
Missing validation of multibyte character length in
PostgreSQL text manipulation allows a database user to
issue crafted queries that achieve a buffer overrun.
That suffices to execute arbitrary code as the operating
system user running the database.
Heap buffer overflow in PostgreSQL pg_trgm allows a
database user to achieve unknown impacts via a crafted
input string. The attacker has limited control over the
byte patterns to be written, but we have not ruled out
the viability of attacks that lead to privilege
escalation.