CVE-2022-41862: Infoleak

Published Jan 30, 2023
·
Updated

A modified, unauthenticated server can send an unterminated string during the establishment of Kerberos transport encryption. When a libpq client application has a Kerberos credential cache and doesn't explicitly disable option "gssencmode", a server can cause libpq to over-read and report an error message containing uninitialized bytes from and following its receive buffer. If libpq's caller somehow makes that message accessible to the attacker, this achieves a disclosure of the over-read bytes. We have not confirmed or ruled out viability of attacks that arrange for a crash or for presence of notable, confidential information in disclosed bytes.

Other sources

In PostgreSQL, a modified, unauthenticated server can send an unterminated string during the establishment of Kerberos transport encryption. In certain conditions a server can cause a libpq client to over-read and report an error message containing uninitialized bytes.

MITRE

PostgreSQL could allow a remote attacker to obtain sensitive information, caused by a client memory disclosure flaw. By sending an unterminated string during the establishment of Kerberos transport encryption, an attacker could exploit this vulnerability to obtain sensitive information.

IBM

Affected Software

17 affected componentsFixes available
redhat/postgresql<5.2
5.2
redhat/postgresql<14.7
14.7
redhat/postgresql<13.10
13.10
redhat/postgresql<12.14
12.14
redhat/postgresql<11.19
11.19
IBM Cloud Pak for Business Automation<=V23.0.1 - V23.0.1-IF001
IBM Cloud Pak for Business Automation<=V21.0.3 - V21.0.3-IF023
IBM Cloud Pak for Business Automation<=V22.0.2 - V22.0.2-IF006 and later fixes V22.0.1 - V22.0.1-IF006 and later fixes V21.0.2 - V21.0.2-IF012 and later fixes V21.0.1 - V21.0.1-IF007 and later fixes V20.0.1 - V20.0.3 and later fixes V19.0.1 - V19.0.3 and later fixes V18.0.0 - V18.0.2 and later fixes
PostgreSQL postgresql>=12.0<12.14
PostgreSQL postgresql>=13.0<13.10
PostgreSQL postgresql>=14.0<14.7
PostgreSQL postgresql>=15.0<15.2
Fedoraproject Fedora=8
redhat Integration Camel K
redhat Integration Camel Quarkus
redhat Integration Service Registry
redhat Enterprise Linux=8.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/postgresql to a version that resolves this vulnerability.

    Fixed in 5.2
  2. Upgrade

    Upgrade redhat/postgresql to a version that resolves this vulnerability.

    Fixed in 14.7
  3. Upgrade

    Upgrade redhat/postgresql to a version that resolves this vulnerability.

    Fixed in 13.10
  4. Upgrade

    Upgrade redhat/postgresql to a version that resolves this vulnerability.

    Fixed in 12.14
  5. Upgrade

    Upgrade redhat/postgresql to a version that resolves this vulnerability.

    Fixed in 11.19

Event History

Jan 30, 2023
Data Sourced
via Red Hat·08:54 PM
DescriptionSeverityAffected Software
Mar 3, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2022-41862?

CVE-2022-41862 is a vulnerability in PostgreSQL that allows a modified, unauthenticated server to send an unterminated string during the establishment of Kerberos transport encryption.

2

How does CVE-2022-41862 affect PostgreSQL?

CVE-2022-41862 affects certain versions of PostgreSQL (up to and excluding version 15.2) where a server can cause a libpq client to over-read and report an error message containing uninitialized bytes.

3

What is the severity of CVE-2022-41862?

CVE-2022-41862 has a low severity rating with a score of 3.7.

4

Which software versions are affected by CVE-2022-41862?

PostgreSQL versions 5.2 up to and excluding 15.2, 8.0 Fedora, Redhat Integration Camel K, Redhat Integration Camel Quarkus, Redhat Integration Service Registry, and Redhat Enterprise Linux 8.0 are affected by CVE-2022-41862.

5

How can I fix CVE-2022-41862?

To fix CVE-2022-41862, users should update their PostgreSQL installations to versions 15.2, 14.7, 13.10, 12.14, or 11.19 depending on the affected version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203