CVE-2021-3393

An information leak was discovered in postgresql in versions before 13.2, before 12.6 and before 11.11. A user having UPDATE permission but not SELECT permission to a particular column could craft queries which, under some circumstances, might disclose values from that column in error messages. An attacker could use this flaw to obtain information stored in a column they are allowed to write but not read.

Weakness

The product generates an error message that includes sensitive information about its environment, users, or associated data.

Affected Software

Potential Mitigations

• Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
• If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
• Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/215.html
• https://cwe.mitre.org/data/definitions/463.html
• https://cwe.mitre.org/data/definitions/54.html
• https://cwe.mitre.org/data/definitions/7.html

References

• https://bugzilla.redhat.com/show_bug.cgi?id=1924005
• https://security.gentoo.org/glsa/202105-32
• https://security.netapp.com/advisory/ntap-20210507-0006/
• https://bugzilla.redhat.com/show_bug.cgi?id=1924005
• https://security.gentoo.org/glsa/202105-32
• https://security.netapp.com/advisory/ntap-20210507-0006/