CVE-2016-0768
First published: Tue Jun 06 2017(Updated: )
PostgreSQL PL/Java after 9.0 does not honor access controls on large objects.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| PostgreSQL Common | <=9.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-0768?
CVE-2016-0768 is classified as a medium severity vulnerability.
How do I fix CVE-2016-0768?
To fix CVE-2016-0768, upgrade PostgreSQL to a version later than 9.0 that properly implements access controls for large objects.
What versions of PostgreSQL are affected by CVE-2016-0768?
CVE-2016-0768 affects all versions of PostgreSQL PL/Java prior to and including 9.0.
What type of vulnerability is CVE-2016-0768?
CVE-2016-0768 is an access control vulnerability related to large objects in PostgreSQL.
Can CVE-2016-0768 lead to unauthorized data access?
Yes, CVE-2016-0768 can lead to unauthorized access to large objects in PostgreSQL due to improper enforcement of access controls.
- agent/type
- agent/references
- agent/weakness
- agent/severity
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/postgresql
- canonical/postgresql common
- version/postgresql common/9.0