| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in PostgreSQL PL-Java up to 1.4.x. It has been rated as critical. This affects an unknown function. The manipulation leads to access control. This vulnerability is documented as CVE-2016-0767. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in PostgreSQL PL-Java up to 1.4.x (Database Software) and classified as critical. This issue affects an unknown function. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
PostgreSQL PL/Java before 1.5.0 allows remote authenticated users with USAGE permission on the public schema to alter the public schema classpath.
The bug was discovered 07/03/2017. The weakness was released 06/06/2017 (Website). It is possible to read the advisory at tada.github.io. The identification of this vulnerability is CVE-2016-0767 since 12/16/2015. The attack may be initiated remotely. The successful exploitation requires a simple authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
Upgrading to version 1.5.0 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-102012 and VDB-102014. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: PostgreSQL PL-Java 1.5.0
Timeline
12/16/2015 🔍06/06/2017 🔍
06/06/2017 🔍
06/07/2017 🔍
07/03/2017 🔍
10/14/2019 🔍
Sources
Advisory: tada.github.ioStatus: Not defined
Confirmation: 🔍
CVE: CVE-2016-0767 (🔍)
GCVE (CVE): GCVE-0-2016-0767
GCVE (VulDB): GCVE-100-102011
See also: 🔍
Entry
Created: 06/07/2017 08:33Updated: 10/14/2019 08:23
Changes: 06/07/2017 08:33 (57), 10/14/2019 08:23 (2)
Complete: 🔍
Cache ID: 216:B09:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.