# CVE-2017-0909: private_address_check contains Incomplete List of Disallowed Inputs

> An attacker can bypass SSRF protections in the private_address_check Ruby gem due to an incomplete blacklist of private network addresses.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-3v3c-r5v2-68ph

## What is CVE-2017-0909?

CVE-2017-0909 is a critical server-side request forgery vulnerability in HackerOne private_address_check ruby gem, published on 16 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The private_address_check ruby gem before 0.4.1 is vulnerable to a bypass due to an incomplete blacklist of common private/local network addresses used to prevent server-side request forgery.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

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

2 open source packages ship an affected version, including private_address_check. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `private_address_check` | RubyGems | All versions | 0.4.1 |
| `private_address_check` | RubyGems | All versions | 0.4.1 |

Products: Private Address Check Project Private Address Check.

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

Upgrade private_address_check to 0.4.1 or later.

## Is CVE-2017-0909 being exploited?

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

## Other vulnerabilities in HackerOne private_address_check ruby gem

- [CVE-2017-0904](https://insights.sbomify.com/CVE-2017-0904/): private_address_check vulnerable to bypass of Resolv.getaddresses method (high 8.1)
- [CVE-2018-3759](https://insights.sbomify.com/CVE-2018-3759/): private_address_check contains race condition (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-0909 is a critical server-side request forgery vulnerability in HackerOne private_address_check ruby gem, published on 16 Nov 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-0909 in the wild and no public exploit code.

Affected packages and fixed versions:
- private_address_check (RubyGems): affected all versions; fixed in 0.4.1
- private_address_check (RubyGems): affected all versions; fixed in 0.4.1

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-0909/ (Markdown: https://insights.sbomify.com/CVE-2017-0909/index.md)
```

## Sources

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

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