Privilege escalation via set_config hook bypass
Published Sep 27, 2021 · Updated Aug 4, 2024
Privilege escalation in the set_user extension module for PostgreSQL before 3.0.0 allows remote attackers to bypass ProcessUtility_hook via set_config. The REL3_0_0 release identifies set_config as bypassing ProcessUtility_hook and adds an object_access_hook to block that modification. The record does not disclose the required session privileges or a more specific post-bypass consequence beyond unauthorized utility-hook bypass.
Summary
What happened
Privilege escalation in the set_user extension module for PostgreSQL before 3.0.0 allows remote attackers to bypass ProcessUtility_hook via set_config. The REL3_0_0 release identifies set_config as bypassing ProcessUtility_hook and adds an object_access_hook to block that modification. The record does not disclose the required session privileges or a more specific post-bypass consequence beyond unauthorized utility-hook bypass.
The record
- CVE
- CVE-2021-41558
- Published
- Sep 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo