Thomas Perale bbf5d842be package/postgresql: security bump to v17.10
For more information about the release, see:
  - https://www.postgresql.org/docs/17/release-17-9.html
  - https://www.postgresql.org/docs/17/release-17-10.html

Fixes the following vulnerabilities:

- CVE-2026-6479:

 Prevent unbounded recursion while processing startup packets
 A malicious client could crash the connected backend by alternating
 rejected SSL and GSS encryption requests indefinitely.

- CVE-2026-6473

 Fix assorted integer overflows in memory-allocation calculations
 Various places were incautious about the possibility of integer overflow
 in calculations of how much memory to allocate. Overflow would lead to
 allocating a too-small buffer which the caller would then write past the
 end of. This would at least trigger server crashes, and probably could
 be exploited for arbitrary code execution. In many but by no means all
 cases, the hazard exists only in 32-bit builds.

- CVE-2026-6476
 Properly quote subscription names in pg_createsubscriber

 The given subscription name was inserted into SQL commands without
 quoting, so that SQL injection could be achieved in the (perhaps
 unlikely) case that the subscription name comes from an untrusted
 source.

- CVE-2026-6638

 Properly quote object names in logical replication origin checks
 ALTER SUBSCRIPTION ... REFRESH PUBLICATION interpolated schema and
 relation names into SQL commands without quoting them, allowing
 execution of arbitrary SQL on the publisher.

- CVE-2026-6473

 Reject over-length options in ts_headline()
 The StartSel, StopSel and FragmentDelimiter strings must not exceed 32Kb
 in length, but this was not checked for. An over-length value would
 typically crash the server.

- CVE-2026-6474

 Guard against malicious time zone names in timeofday() and pg_strftime()
 A crafted time zone setting could pass % sequences to snprintf(),
 potentially causing crashes or disclosure of server memory. Another path
 to similar results was to overflow the limited-size output buffer used
 by pg_strftime().

- CVE-2026-6472

 When creating a multirange type, ensure the user has CREATE privilege on
 the schema specified for the multirange type.

 The multirange type can be put into a different schema than its parent
 range type, but we neglected to apply the required privilege check when
 doing so.

- CVE-2026-6478

 Use timing-safe string comparisons in authentication code.

 Use timingsafe_bcmp() instead of memcpy() or strcmp() when checking
 passwords, hashes, etc. It is not known whether the data dependency of
 those functions is usefully exploitable in any of these places, but in
 the interests of safety, replace them.

- CVE-2026-6477

 Mark PQfn() as unsafe, and avoid using it within libpq

 For a non-integral result type, PQfn() is not passed the size of the
 output buffer, so it cannot check that the data returned by the server
 will fit. A malicious server could therefore overwrite client memory.
 This is unfixable without an API change, so mark the function as
 deprecated. Internally to libpq, use a variant version that can apply
 the missing check.

- CVE-2026-6475

 Prevent path traversal in pg_basebackup and pg_rewind

 These applications failed to validate output file paths read from their
 input, so that a malicious source could overwrite any file writable by
 these applications. Constrain where data can be written by rejecting
 paths that are absolute or contain parent-directory references.

- CVE-2026-6473

 Guard against field overflow within contrib/intarray's query_int type
 and contrib/ltree's ltxtquery type.

 Parsing of these query structures did not check for overflow of 16-bit
 fields, so that construction of an invalid query tree was possible.
 This can crash the server when executing the query.

- CVE-2026-6473

 Guard against overly long values of contrib/ltree's lquery type.

 Values with more than 64K items caused internal overflows, potentially
 resulting in stack smashes or wrong answers.

- CVE-2026-6637

 Prevent SQL injection and buffer overruns in contrib/spi.

 check_foreign_key() was insufficiently careful about quoting key
 values, and also used fixed-length buffers for constructing queries.
 While this module is only meant as example code, it still shouldn't
 contain such dangerous errors.

(cherry picked from commit 9fb64dfc24)
Signed-off-by: Thomas Perale <thomas.perale@mind.be>
2026-05-29 16:43:18 +02:00
2026-04-10 12:20:23 +02:00
2025-01-15 21:30:31 +01:00
2026-05-20 11:56:06 +02:00
2026-05-20 14:00:48 +02:00
2026-01-15 09:36:08 +01:00
2026-04-03 12:21:44 +02:00

Buildroot is a simple, efficient and easy-to-use tool to generate embedded
Linux systems through cross-compilation.

The documentation can be found in docs/manual. You can generate a text
document with 'make manual-text' and read output/docs/manual/manual.text.
Online documentation can be found at https://buildroot.org/docs.html

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the target architecture and the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) find the kernel, bootloader, root filesystem, etc. in output/images

You do not need to be root to build or run buildroot.  Have fun!

Buildroot comes with a basic configuration for a number of boards. Run
'make list-defconfigs' to view the list of provided configurations.

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org
You can also find us on #buildroot on OFTC IRC.

If you would like to contribute patches, please read
https://buildroot.org/manual.html#submitting-patches
Description
No description provided
Readme 206 MiB
Languages
Makefile 62.5%
Python 19%
C 8.5%
Shell 6.1%
PHP 1.4%
Other 2.1%