# CVE-2017-7485: Security feature bypass in PostgreSQL

> An active Man-in-the-Middle attacker can strip SSL/TLS protection from PostgreSQL connections if the PGREQUIRESSL environment variable is used, exposing data.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-7485, CLEANSTART-2026-KW67174, GHSA-742m-4pjq-x8qf, UBUNTU-CVE-2017-7485

## What is CVE-2017-7485?

CVE-2017-7485 is a medium-severity vulnerability in Postgresql Postgresql, published on 12 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In PostgreSQL 9.3.x before 9.3.17, 9.4.x before 9.4.12, 9.5.x before 9.5.7, and 9.6.x before 9.6.3, it was found that the PGREQUIRESSL environment variable was no longer enforcing a SSL/TLS connection to a PostgreSQL server. An active Man-in-the-Middle attacker could use this flaw to strip the SSL/TLS protection from a connection between a client and a server.

Weakness: CWE-311 (Missing Encryption of Sensitive Data), CWE-390 (Detection of Error Condition Without Action)

## Which versions are affected by CVE-2017-7485?

It affects 1 product.


Products: Postgresql Postgresql.

## How do I fix CVE-2017-7485?

Upgrade to a fixed version.

## Is CVE-2017-7485 being exploited?

There is no known exploitation of CVE-2017-7485 in the wild and no public exploit code.

## Other vulnerabilities in Postgresql Postgresql

- [CVE-2013-1902](https://insights.sbomify.com/CVE-2013-1902/): Information disclosure in n/a (critical 10.0)
- [CVE-2013-1903](https://insights.sbomify.com/CVE-2013-1903/): Information disclosure in n/a (critical 10.0)
- [CVE-2007-3279](https://insights.sbomify.com/CVE-2007-3279/): Privilege escalation in n/a (critical 10.0)
- [CVE-2002-1399](https://insights.sbomify.com/CVE-2002-1399/): Integer overflow in n/a (critical 10.0)
- [CVE-2016-3065](https://insights.sbomify.com/CVE-2016-3065/): Information disclosure in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7485 and fix it if it is affected.

What it is: CVE-2017-7485 is a medium-severity vulnerability in Postgresql Postgresql, published on 12 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-7485 in the wild and no public exploit code.

Affected product: Postgresql Postgresql. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-7485/ (Markdown: https://insights.sbomify.com/CVE-2017-7485/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7485
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7485
- OSV: https://osv.dev/vulnerability/CVE-2017-7485

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-7485/
Summaries are generated and may contain mistakes; the official description above is the record.