A vulnerability was found in PostgreSQL with the use of the MERGE command, which fails to test new rows against row security policies defin…
A vulnerability was found in PostgreSQL with the use of the MERGE command, which fails to test new rows against row security policies defined for UPDATE and SELECT. If UPDATE and SELECT policies forbid some rows that INSERT policies do not forbid, a user could store such rows.
The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.
https://cwe.mitre.org/data/definitions/1220.html →Open in CWE collection →In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.
https://capec.mitre.org/data/definitions/1.html →Open in CAPEC collection →An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack.
https://capec.mitre.org/data/definitions/180.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| postgresql | Tracked | |
| postgresql | Tracked | |
| postgresql | Tracked | |
| postgresql | Tracked | |
| postgresql-10 | Tracked | |
| postgresql-11 | Tracked | |
| postgresql-12 | Tracked | |
| postgresql-12 | Tracked | |
| postgresql-13 | Tracked | |
| postgresql-14 | Tracked | |
| postgresql-15 | Tracked | |
| postgresql-15 | Tracked | |
| postgresql-15 | Tracked | |
| postgresql-15 | Tracked | |
| postgresql-15 | Tracked | |
| postgresql-15 | Tracked | |
| postgresql-15 | Tracked | |
| postgresql-9.1 | Tracked | |
| postgresql-9.3 | Tracked | |
| postgresql-9.5 | Tracked |