Pl\/javaApplication · Pl\/java Project
CVE-2016-2192
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 to alter type mappings for types they do not own.
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 confidencePL/Java before version 1.5.0 contains an authorization bypass vulnerability where remote authenticated database users can alter type mappings for database types they do not own. This allows privilege escalation through unauthorized modification of type associations in the PostgreSQL database.
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.
-
Check installed PL/Java versionQuery the pg_extension system catalog or use SELECT sqlj.get_version(); to retrieve the currently installed PL/Java version numberAffected if The version number is 1.4.3 or lower (any version <= 1.4.3)
-
Verify PL/Java type mapping functionality is accessibleCheck if the sqlj type mapping functions (such as sqlj.set_type_mapping or similar) are available to database users by examining grants on the sqlj schemaAffected if Authenticated database users have access to type mapping functions without proper ownership validation
-
Inspect type mapping ownershipQuery the pg_catalog.pg_type system catalog joined with sqlj tables to list all type mappings and their owners, looking for mappings where the type owner differs from the mapping ownerAffected if Type mappings exist for types owned by one user but mapped by a different, non-owner user
-
Review recent type mapping modificationsExamine PostgreSQL logs for recent ALTER or CREATE statements on sqlj type mappings, or query history if logging is enabledAffected if Type mapping changes were performed by users who do not own the underlying database types
A user is affected if PL/Java version is 1.4.3 or lower AND type mapping functions are accessible to authenticated users who did not create the types.
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 to patch the authorization flaw. Ensure proper type ownership permissions are reviewed after upgrading.
Fix this in Pl\/java
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2192 — 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-2192 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