dbcve.org
Pgadmin 4Application · Pgadmin

CVE-2024-9014

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-23
Fix available
A fix is available. Upgrade to 8.12 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
pgAdmin versions 8.11 and earlier are vulnerable to a security flaw in OAuth2 authentication. This vulnerability allows an attacker to potentially obtain the client ID and secret, leading to unauthorized access to user data.

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 confidence

pgAdmin versions 8.11 and earlier contain an OAuth2 authentication vulnerability that allows attackers to potentially obtain the client ID and secret. This information disclosure could enable unauthorized access to user data through the OAuth2 authentication flow.

MitigationUpgrade pgAdmin to a version newer than 8.11. Review OAuth2 configuration settings to ensure no credentials are exposed and rotate any potentially compromised client IDs and secrets.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pgadmin 4Application
Affected:< 8.12

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed pgAdmin version
    Check the pgAdmin web interface footer or use the pgAdmin Python package version command to determine the installed version number
    Affected if The installed version is 8.11 or earlier (less than 8.12)
  2. Verify OAuth2 authentication is configured
    Review pgAdmin configuration files for OAuth2-related settings such as OAUTH2_CONFIG, OAUTH2_CLIENT_ID, or similar OAuth2 provider configurations
    Affected if OAuth2 authentication is enabled and configured in the pgAdmin environment
  3. Inspect OAuth2 credential storage
    Examine configuration files (config_local.py, config.py, or environment variables) for OAuth2 client ID and secret values stored in plain text or with weak protection
    Affected if OAuth2 client ID and secret are found stored in configuration files or environment variables
  4. Check for credential exposure in logs
    Search pgAdmin server logs for any OAuth2 client ID or secret strings that may have been inadvertently logged
    Affected if OAuth2 credentials appear in log files or error traces

A user is affected if running pgAdmin version 8.11 or earlier with OAuth2 authentication enabled and credentials are present in accessible configuration files or logs

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 8.12 or later
Fixed in 8.12
Interim mitigation

Upgrade pgAdmin to a version newer than 8.11. Review OAuth2 configuration settings to ensure no credentials are exposed and rotate any potentially compromised client IDs and secrets.

Recommended fix Moderate confidence

pgAdmin 4 version 8.12

  1. Back up your current pgAdmin configuration and database before upgrading
  2. Download pgAdmin 4 version 8.12 or later from the official pgAdmin website (https://www.pgadmin.org/download/)
  3. For containerized deployments: Update your Docker image tag to pgadmin4:8.12 or later
  4. For package-based installations: Install the new pgAdmin4 package for your operating system
  5. For source installations: Pull the latest code from the pgAdmin repository and reinstall
  6. After upgrade, verify OAuth2 authentication is working correctly
  7. Ensure your OAuth2 client ID and secret have been rotated as a precaution
Caveat No major breaking changes expected for typical upgrades; minor changes to OAuth2 configuration may be required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pgadmin 4 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9014 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9014 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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