Horizon Alert
Summary of the vulnerability and why it matters
A critical security issue has been identified in Postgres Enterprise Manager (PEM), affecting the PEM backend database. This vulnerability could allow unauthorized users to execute arbitrary SQL commands with superuser privileges, potentially leading to significant data compromise or system control. The primary concern is confirming if your PEM environment is exposed and requires review.
- SQL commands can be run with high privileges.
- This impacts PEM backend database administrative functions.
- Confirm relevance and exposure of your PEM environment.
Attack Path
How an attacker could exploit the issue
An attacker with access to the PEM backend database could manipulate the environment to execute arbitrary SQL commands with superuser privileges. This is achieved by exploiting specific functions that incorrectly handle search paths, allowing the attacker to substitute malicious objects for legitimate ones. The vulnerability can lead to the execution of any SQL command that the superuser can run.
- Attacker needs database access.
- Attacker creates malicious database objects.
- Risk of arbitrary SQL execution.
Live Threat
Current exploitation, exposure, and threat context
In the PEM backend database, several functions could allow any user to execute arbitrary SQL with superuser privileges when a safe search_path is not set. This could affect any PEM user who can connect to the database.
- Arbitrary SQL execution with superuser privileges.
- Creation of malicious objects in specific schemas.
- Unauthorized access to and modification of database data.
Operational Fix
Recommended remediation, mitigation, and detection steps
Given that this vulnerability resides within the Postgres Enterprise Manager (PEM) backend database, the platform team or database administration team responsible for PEM operations is likely accountable for addressing it. The initial practical step involves identifying all PEM instances, verifying their reachability and business criticality, locating the specific ownership of each instance, and then developing a remediation plan based on the assessed risk.
- Platform or DBA teams own the issue.
- Verify PEM instance reachability and criticality.
- Plan remediation based on assessed risk.