CVE-2024-45624
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedExposure of sensitive information due to incompatible policies issue exists in Pgpool-II. If a database user accesses a query cache, table data unauthorized for the user may be retrieved.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePgpool-II's query cache feature does not properly enforce authorization policies, allowing database users to retrieve table data they are not authorized to access. When query caching is enabled, cached query results may be returned to users without proper validation against the user's actual permissions on the underlying tables.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Pgpool-II installation and versionRun 'psql -c "SELECT version();"' or check your package manager (dpkg -l | grep pgpool, rpm -qa | grep pgpool). Compare the version to any official Pgpool-II release notes for your distribution.Affected if The installed version is unpatched and older than the version that addresses this authorization bypass.
-
Verify if query caching is enabledCheck Pgpool-II configuration files (typically pgpool.conf) for 'query_cache' or 'memqcache' settings. You can also run 'SHOW query_cache;' or similar diagnostic command if available in your deployment.Affected if query_cache is set to 'on' or memqcache is configured and active.
-
Inspect cache storage configurationExamine pgpool.conf for 'memqcache_method', 'memqcache_total_cache', and 'memqcache_max_cache' parameters. Check if shared memory or memory-based caching is in use.Affected if Memory-based query caching (memqcache) is actively storing query results.
-
Review backend PostgreSQL user permissionsConnect directly to the backend PostgreSQL databases as an administrator and audit SELECT permissions on sensitive tables using '\dp' or 'SELECT * FROM information_schema.table_privileges' for tables in databases served by Pgpool-II.Affected if Users have different permission levels between direct PostgreSQL access and access through Pgpool-II, indicating cached results may bypass checks.
-
Test cache behavior with restricted dataAs a limited-privilege user, query a table you have access to through Pgpool-II, then verify the cached query. As a different user without permissions to that table, attempt the same query through Pgpool-II to see if cached results are returned.Affected if A user without table permissions receives cached data that was originally queried by a privileged user.
A user is affected if they run an unpatched Pgpool-II version with query caching enabled, and cached query results can be retrieved by users lacking proper table permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReview and enforce proper access control policies on query cache configuration, or disable query caching if proper authorization cannot be ensured. Consider upgrading to a patched version if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45624 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-45624 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data