CVE-2017-16082 Vulnerability Analysis & Exploit Details

CVE-2017-16082
Vulnerability Scoring

9.8

/10

Critical Risk

As a catastrophic security flaw, CVE-2017-16082 has severe implications, demanding immediate intervention.

Attack Complexity Details

Attack Complexity: Low
Exploits can be performed without significant complexity or special conditions.
Attack Vector: Network
Vulnerability is exploitable over a network without physical access.
Privileges Required: None
No privileges are required for exploitation.
Scope: Unchanged
Exploit remains within the originally vulnerable component.
User Interaction: None
No user interaction is necessary for exploitation.

CVE-2017-16082 Details

Status: Modified

Last updated: 🕒 21 Nov 2024, 03:15 UTC
Originally published on: 🕑 07 Jun 2018, 02:29 UTC

Time between publication and last update: 2359 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE-2017-16082 Vulnerability Summary

CVE-2017-16082: A remote code execution vulnerability was found within the pg module when the remote database or query specifies a specially crafted column name. There are 2 likely scenarios in which one would likely be vulnerable. 1) Executing unsafe, user-supplied sql which contains a malicious column name. 2) Connecting to an untrusted database and executing a query which returns results where any of the column names are malicious.

Assessing the Risk of CVE-2017-16082

Access Complexity Graph

The exploitability of CVE-2017-16082 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2017-16082

With low attack complexity and no required privileges, CVE-2017-16082 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2017-16082, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2017-16082, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: High
Exploiting CVE-2017-16082 can result in unauthorized access to sensitive data, severely compromising data privacy.
Integrity: High
CVE-2017-16082 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
Availability: High
CVE-2017-16082 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 23.333% (probability of exploit)

EPSS Percentile: 96.68% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 3.319999999999993% of others.

CVE-2017-16082 References

External References

CWE Common Weakness Enumeration

CWE-94

CAPEC Common Attack Pattern Enumeration and Classification

Code Injection CAPEC-242 An adversary exploits a weakness in input validation on the target to inject new code into that which is currently executing. This differs from code inclusion in that code inclusion involves the addition or replacement of a reference to a code file, which is subsequently loaded by the target and used as part of the code of some application.
Leverage Executable Code in Non-Executable Files CAPEC-35 An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
Manipulating User-Controlled Variables CAPEC-77 This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.

Vulnerable Configurations

cpe:2.3:a:node-postgres:pg:2.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.2.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.2.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.3.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.3.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.3.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.3.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.4.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.4.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.5.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.5.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.5.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.5.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.6.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.6.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.6.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.6.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.6.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.6.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.7.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.7.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.8.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.9.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.9.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.10.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.10.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.11.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.11.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.11.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:2.11.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.2.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.2.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.3.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.3.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.4.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.5.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.5.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.6.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.6.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.6.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.6.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.6.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.6.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.6.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:3.6.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.0.0:-:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.0.0:-:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.0.0:beta2:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.0.0:beta2:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.2.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.2.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.3.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.3.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.6:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.4.6:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.6:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:4.5.6:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:5.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:5.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.0.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.6:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.1.6:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.2.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.2.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.2.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.2.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.2.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.2.4:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.2.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.2.5:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.3.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.3.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.3.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.3.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.3.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.3.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.4.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.4.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.4.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:6.4.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.0.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.0.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.0.2:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.0.3:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.1.0:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.1.1:*:*:*:*:node.js:*:*
cpe:2.3:a:node-postgres:pg:7.1.1:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2017-16082: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

CVE-2025-3800 – A vulnerability has been found in WCMS 11 and classified as critical. Affected by this vulnerability is an unknown functionality of the file app/co...
CVE-2025-3799 – A vulnerability, which was classified as critical, was found in WCMS 11. Affected is an unknown function of the file app/controllers/AnonymousContr...
CVE-2025-3798 – A vulnerability, which was classified as critical, has been found in WCMS 11. This issue affects the function sub of the file app/admin/AdvadminCon...
CVE-2025-3661 – The SB Chart block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘className’ parameter in all versions up to, and inclu...
CVE-2025-3404 – The Download Manager plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the savePackage func...