CVE-2023-2455: Input Validation

Published May 12, 2023
·
Updated

CVE-2023-2455: Row security policies disregard user ID changes after inlining.

Versions Affected: 11 - 15. This problem is quite old.

While CVE-2016-2193 fixed most interaction between row security and user ID changes, it missed a scenario involving function inlining. This leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy.

https://www.postgresql.org/support/security/CVE-2023-2455/

Other sources

Row security policies disregard user ID changes after inlining; PostgreSQL could permit incorrect policies to be applied in certain cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy.

— Ubuntu

Affected Software

22 affected componentsFixes available
debian/postgresql-11<=11.16-0+deb10u1
11.22-0+deb10u2
debian/postgresql-13
13.13-0+deb11u113.14-0+deb11u1
debian/postgresql-15
15.5-0+deb12u115.6-0+deb12u1
ubuntu/postgresql-10<10.23-0ubuntu0.18.04.2
10.23-0ubuntu0.18.04.2
ubuntu/postgresql-12<12.15-0ubuntu0.20.04.1
12.15-0ubuntu0.20.04.1
ubuntu/postgresql-14<14.8-0ubuntu0.22.04.1
14.8-0ubuntu0.22.04.1
ubuntu/postgresql-14<14.8-0ubuntu0.22.10.1
14.8-0ubuntu0.22.10.1
ubuntu/postgresql-15<15.3-0ubuntu0.23.04.1
15.3-0ubuntu0.23.04.1
redhat/PostgreSQL<15.3
15.3
redhat/PostgreSQL<14.8
14.8
redhat/PostgreSQL<13.11
13.11
redhat/PostgreSQL<12.15
12.15
redhat/PostgreSQL<11.20
11.20
PostgreSQL postgresql>=11.0<11.20
PostgreSQL postgresql>=12.0<12.15
PostgreSQL postgresql>=13.0<13.11
PostgreSQL postgresql>=14.0<14.8
PostgreSQL postgresql>=15.0<15.3
redhat Software Collections
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
Fedoraproject Fedora=38

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/postgresql-11 to a version that resolves this vulnerability.

    Fixed in 11.22-0+deb10u2
  2. Upgrade

    Upgrade debian/postgresql-13 to a version that resolves this vulnerability.

    Fixed in 13.13-0+deb11u1Fixed in 13.14-0+deb11u1
  3. Upgrade

    Upgrade debian/postgresql-15 to a version that resolves this vulnerability.

    Fixed in 15.5-0+deb12u1Fixed in 15.6-0+deb12u1
  4. Upgrade

    Upgrade ubuntu/postgresql-10 to a version that resolves this vulnerability.

    Fixed in 10.23-0ubuntu0.18.04.2
  5. Upgrade

    Upgrade ubuntu/postgresql-12 to a version that resolves this vulnerability.

    Fixed in 12.15-0ubuntu0.20.04.1
  6. Upgrade

    Upgrade ubuntu/postgresql-14 to a version that resolves this vulnerability.

    Fixed in 14.8-0ubuntu0.22.04.1
  7. Upgrade

    Upgrade ubuntu/postgresql-14 to a version that resolves this vulnerability.

    Fixed in 14.8-0ubuntu0.22.10.1
  8. Upgrade

    Upgrade ubuntu/postgresql-15 to a version that resolves this vulnerability.

    Fixed in 15.3-0ubuntu0.23.04.1
  9. Upgrade

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

    Fixed in 15.3
  10. Upgrade

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

    Fixed in 14.8
  11. Upgrade

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

    Fixed in 13.11
  12. Upgrade

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

    Fixed in 12.15
  13. Upgrade

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

    Fixed in 11.20

Event History

May 12, 2023
CVE Published
via Ubuntu·12:00 AM
May 16, 2023
Data Sourced
via Red Hat·10:07 AM
DescriptionSeverityAffected Software
Jun 9, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Jan 12, 2024
Data Sourced
via Launchpad·12:16 AM
Description

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2023-2455?

The severity of CVE-2023-2455 is medium (5.4).

2

What is the affected software for CVE-2023-2455?

The affected software for CVE-2023-2455 includes PostgreSQL versions 10.23-0ubuntu0.18.04.2, 12.15-0ubuntu0.20.04.1, 14.8-0ubuntu0.22.04.1, 14.8-0ubuntu0.22.10.1, 15.3-0ubuntu0.23.04.1, Debian versions 11.21-0+deb10u2, 13.11-0+deb11u1, 15.3-0+deb12u1, 15.4-3, Redhat versions 15.3, 14.8, 13.11, 12.15, and 11.20, and Redhat Enterprise Linux versions 8.0 and 9.0.

3

What is the vulnerability description of CVE-2023-2455?

CVE-2023-2455 is a vulnerability where row security policies in PostgreSQL disregard user ID changes after inlining, potentially allowing incorrect policies to be applied.

4

How do I fix CVE-2023-2455?

To fix CVE-2023-2455, users should update to the latest version of PostgreSQL, as provided in the affected software list.

5

Where can I find more information about CVE-2023-2455?

More information about CVE-2023-2455 can be found at the following references: [1] [2] [3].

Company

Resources

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