PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released

(postgresql.org)

77 points | by plaur782 4 hours ago ago

9 comments

  • ianberdin 2 hours ago ago

    Looking at all these security patches reminded me of when I was a kid and I thoroughly cleaned my apartment, wiped away every bit of dust in every single crevice, and then a couple of days later it was all back again. And I thought: am I really going to be doing this my whole life?

    • rglover 3 minutes ago ago

      Narrator: yes.

  • lfittl an hour ago ago

    FWIW, I found it easier to look at the release notes (https://www.postgresql.org/docs/release/18.7/) to understand the overall scope of the CVEs - from the announcement the individual CVE pages are linked, but its hard to scan.

  • zulux 3 hours ago ago

    Mega patches like this, in my opinion, should be treated as mandatory patches. If I were trying to get a significant security update into the field in the age of LLM drama, this is how I would do it.

    • levkk 2 hours ago ago

      Most databases run offline and don't allow arbitrary SQL statements. SQL injections are generally eliminated by using the extended protocol.

      So, yes, if you're running multi-tenant Postgres as a public service, you should upgrade. Everyone else is in no rush.

      • perlgeek 2 hours ago ago

        No rush, but don't wait too long either.

        Yes, the application above it should prevent SQL injection, but if it's imperfect, you don't want an attacker to turn SQL injection into RCE.

    • fock 2 hours ago ago

      then, what would you do if you were an adversary trying to push your xz-style vulnerability to every place known to man?

    • ltbarcly3 3 hours ago ago

      So you're in favor of applying security patches? Controversial opinion.

  • simonw 3 hours ago ago

    "This release fixes 52 security vulnerabilities and over 140 bugs reported over the last several months."