Pl\/javaApplication · Pl\/java Project
CVE-2016-0767
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 · uneditedPostgreSQL PL/Java before 1.5.0 allows remote authenticated users with USAGE permission on the public schema to alter the public schema classpath.
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 · high confidencePostgreSQL PL/Java before version 1.5.0 contains a flaw where authenticated database users with USAGE permission on the public schema can alter the public schema's classpath. This authorization bypass could allow a less-privileged user to manipulate class loading behavior, potentially leading to arbitrary code execution within the database backend.
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
Pl\/javaApplication
<= 1.4.3CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Verify PL/Java extension is installedRun: SELECT extname, extversion FROM pg_extension WHERE extname = 'pljava';Affected if No rows returned means PL/Java is not installed (not affected). If rows exist, proceed to version check.
-
Determine installed PL/Java versionRun: SELECT extversion FROM pg_extension WHERE extname = 'pljava'; Compare the result to the affected range: versions <= 1.4.3 are vulnerable.Affected if If the version is 1.4.3 or lower, the environment is affected by this CVE.
-
Check for USAGE permission on public schemaRun: SELECT grantee, privilege_type FROM information_schema.usage_privileges WHERE grantee != 'PUBLIC' AND schema_name = 'public';Affected if If any non-admin or untrusted users have USAGE permission on the public schema, they can exploit this vulnerability.
-
Inspect public schema classpath configurationRun: SELECT * FROM pg_settings WHERE name LIKE 'pljava.classpath%'; Check if the public schema classpath has been modified.Affected if If classpath entries exist for the public schema and untrusted users have USAGE permission, the flaw can be exploited.
A user is affected if PL/Java version 1.4.3 or lower is installed AND untrusted database users have USAGE permission on the public schema.
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 dataUpgrade PL/Java to version 1.5.0 or later. Additionally, review and restrict USAGE permissions on schemas to only trusted users, especially in multi-tenant or shared database environments.
Fix this in Pl\/java
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0767 — 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-2016-0767 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