Moderate: postgresql security update

postgresql Updated 02 Oct 2025

Summary

11/04/2023
N/A
Yes i
Unrated
Not published

ALSA-2023:1693: Moderate: postgresql security update. Affects postgresql versions < 13.10-1.el9_1. Fixed in 13.10-1.el9_1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

PostgreSQL is an advanced object-relational database management system (DBMS). It is widely used for storing and managing structured data in various applications. PostgreSQL provides a rich set of features and is known for its reliability, scalability, and extensibility.

Vulnerability Detail

The vulnerability (CVE-2022-2625) in PostgreSQL allows extension scripts to replace objects that do not belong to the extension. This can lead to unauthorized access, data corruption, or privilege escalation. Another vulnerability (CVE-2022-41862) allows a client to disclose memory when connecting with Kerberos to a modified server. An attacker could exploit this to obtain sensitive information from the server's memory.

How To Fix

Minimum fixed version

13.10-1.el9_1

This is the first release that contains the fix.

sudo dnf update postgresql

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There are no specific workarounds mentioned for this vulnerability. It is advised to apply the security update as soon as possible to mitigate the risk.

Conclusion

PostgreSQL has released a security update to address the identified vulnerabilities. It is important to update PostgreSQL to the latest version to protect against potential exploits. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for postgresql →

Share this vulnerability

FAQ

PostgreSQL is an advanced object-relational database management system (DBMS) known for its reliability, scalability, and extensibility.

CVE-2022-2625 allows extension scripts to replace objects not belonging to the extension, which can lead to unauthorized access, data corruption, or privilege escalation.

CVE-2022-41862 allows a client to disclose memory when connecting with Kerberos to a modified server, potentially exposing sensitive information from the server's memory.

To fix the vulnerability, update PostgreSQL to version 13.10-1.el9_1 or later.

There are no specific workarounds mentioned for this vulnerability. It is recommended to apply the security update.

Related vulnerabilities

Recent vulnerabilities recorded for postgresql.

How To Fix

Minimum fixed version

13.10-1.el9_1

This is the first release that contains the fix.

sudo dnf update postgresql

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback