MEDIUM CVSS 6.5
Published: 2017-11-22

CVE-2017-15099

postgresql postgresql Security Advisory (CVE-2017-15099)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2017-15099?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2017-15099 impacting postgresql postgresql. Evaluated with CVSS Base Score of 6.5 (MEDIUM).

Original NVD Description

Source: NIST NVD
INSERT ... ON CONFLICT DO UPDATE commands in PostgreSQL 10.x before 10.1, 9.6.x before 9.6.6, and 9.5.x before 9.5.10 disclose table contents that the invoker lacks privilege to read. These exploits affect only tables where the attacker lacks full read access but has both INSERT and UPDATE privileges. Exploits bypass row level security policies and lack of SELECT privilege.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
Low (PR:L)
Standard user access required
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
High (C:H)
Total information disclosure
Integrity
None (I:N)
No system modification impact
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product postgresql / postgresql
Affected Versions 9.5
Weakness Enumeration CWE-200

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2017-15099 impacting postgresql postgresql.

⚡ Nuclei Detection Template (YAML) cve-2017-15099.yaml
id: cve-2017-15099

info:
  name: postgresql postgresql - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: medium
  description: |
    Automated signature & scanner for CVE-2017-15099 affecting postgresql postgresql.
    Evaluation: INSERT ... ON CONFLICT DO UPDATE commands in PostgreSQL 10.x before 10.1, 9.6.x before 9.6.6, and 9.5.x before 9.5.10 disclose table contents that the...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2017-15099
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
    cvss-score: 6.5
    cve-id: CVE-2017-15099
    cwe-id: CWE-200
  tags: cve,cve-2017-15099,postgresql,postgresql,medium

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "postgresql"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2017-15099.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2017-15099
# Target: postgresql postgresql | CVSS: 6.5 (MEDIUM)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2017-15099 (postgresql postgresql)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against postgresql postgresql scope (9.5).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2017-15099.sh
# Recommended Remediation & Patching Commands for CVE-2017-15099
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install postgresql 2>/dev/null || \
sudo dnf upgrade postgresql 2>/dev/null || \
sudo yum update postgresql

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i postgresql 2>/dev/null || rpm -qa | grep -i postgresql

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2017-15099 in postgresql postgresql?

Review vendor-specific security notices and update postgresql postgresql packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2017-15099?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2017-15099?

CVE-2017-15099 is classified with a CVSS 3.1 Base Score of 6.5 (MEDIUM). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
6.5
MEDIUM SEVERITY
CVE ID CVE-2017-15099
Weakness CWE-200
Vendor postgresql
Product postgresql
Published 2017-11-22
Vector CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N