The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Incorrect Privilege Assignment vulnerabilities in an interactive lesson.
Start learningUpgrade RHEL:8
postgresql:13/postgresql-plperl
to version 0:13.18-1.module+el8.10.0+22549+cf2ec3d9 or higher.
This issue was patched in RHSA-2024:10832
.
Note: Versions mentioned in the description apply only to the upstream postgresql:13/postgresql-plperl
package and not the postgresql:13/postgresql-plperl
package as distributed by RHEL
.
See How to fix?
for RHEL:8
relevant fixed versions and status.
Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.