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.
[
{
"events": [
{
"introduced": "11.0"
},
{
"fixed": "11.20"
}
]
},
{
"events": [
{
"introduced": "12.0"
},
{
"fixed": "12.15"
}
]
},
{
"events": [
{
"introduced": "13.0"
},
{
"fixed": "13.11"
}
]
},
{
"events": [
{
"introduced": "14.0"
},
{
"fixed": "14.8"
}
]
},
{
"events": [
{
"introduced": "15.0"
},
{
"fixed": "15.3"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "8.0"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "9.0"
}
]
},
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "38"
}
]
}
]
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-2455.json"