Security readout for executives and security teams
Plain-English summary
CVE-2016-0767 affects PostgreSQL PL/Java before 1.5.0. An authenticated database user with USAGE permission on the public schema could change that schema's classpath. The main concern is unauthorized control over shared PL/Java behavior, not unauthenticated internet compromise.
Executive priority
Treat this as a targeted database privilege-risk issue. It is not evidenced as actively exploited, but it matters where PL/Java is deployed in shared or multi-tenant PostgreSQL environments.
Technical view
The issue is an access-control flaw in PL/Java before 1.5.0 involving modification of the public schema classpath by remote authenticated users who have USAGE on that schema. The provided sources do not include CVSS, CWE, exploit details, or a detailed vendor mitigation beyond the version boundary.
Likely exposure
Exposure is likely limited to PostgreSQL deployments using PL/Java versions before 1.5.0 where untrusted or lower-privileged authenticated users have USAGE on the public schema.
Exploitation context
The source bundle does not show active exploitation, and CISA KEV status is false. Exploitation requires authentication and the stated schema permission. No public exploit workflow is included in the provided evidence.
Researcher notes
Key missing evidence includes CVSS scoring, CWE mapping, exploit maturity, and detailed patch notes in the source bundle. Validation should focus on PL/Java version, public schema permissions, and whether untrusted authenticated users exist.
Mitigation direction
- Identify PostgreSQL instances using PL/Java before 1.5.0.
- Upgrade PL/Java to 1.5.0 or later where applicable.
- Review vendor release notes before changing production systems.
- Restrict public schema USAGE to users that genuinely need it.
- Audit database roles with access to shared PL/Java schemas.
Validation and detection
- Inventory installed PL/Java versions across PostgreSQL environments.
- Confirm whether public schema USAGE is granted to non-administrative users.
- Review schema classpath change history where audit data exists.
- Check vendor release notes for the applicable fixed version.
- Prioritize systems with multi-user or externally reachable database access.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2016-0767 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://tada.github.io/pljava/releasenotes.htmlCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.