How severe is GHSA-hxhj-hp9m-qwc4?

No CVSS score has been assigned to GHSA-hxhj-hp9m-qwc4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hxhj-hp9m-qwc4?

GHSA-hxhj-hp9m-qwc4 affects the following packages: private_address_check (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-hxhj-hp9m-qwc4?

Update private_address_check to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hxhj-hp9m-qwc4 is resolved across your whole dependency graph.

How do I detect GHSA-hxhj-hp9m-qwc4 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for private_address_check. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-hxhj-hp9m-qwc4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-hxhj-hp9m-qwc4?

O3 pinpoints whether GHSA-hxhj-hp9m-qwc4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-hxhj-hp9m-qwc4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-hxhj-hp9m-qwc4 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hxhj-hp9m-qwc4?

GHSA-hxhj-hp9m-qwc4 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 83th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hxhj-hp9m-qwc4?

GHSA-hxhj-hp9m-qwc4 is classified as CWE-242 (CWE-242), CWE-755 (CWE-755). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hxhj-hp9m-qwc4 published, and has it been updated?

GHSA-hxhj-hp9m-qwc4 was published on November 29, 2017 and was last updated on November 30, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

GHSA-hxhj-hp9m-qwc4

Fix: jtdowney/private_address_check@58a0d7f

GHSA-hxhj-hp9m-qwc4 is a CWE-242 vulnerability in private_address_check. O3 Security confirms whether GHSA-hxhj-hp9m-qwc4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

private_address_check vulnerable to bypass of Resolv.getaddresses method

Also known asCVE-2017-0904

Published

Nov 29, 2017

Updated

Nov 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

💎private_address_check

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

The private_address_check ruby gem before 0.4.0 is vulnerable to a bypass due to use of Ruby's Resolv.getaddresses method, which is OS-dependent and should not be relied upon for security measures, such as when used to blacklist private network addresses to prevent server-side request forgery.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`private_address_check`	all versions	0.4.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for private_address_check. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update private_address_check to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hxhj-hp9m-qwc4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hxhj-hp9m-qwc4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hxhj-hp9m-qwc4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The private_address_check ruby gem before 0.4.0 is vulnerable to a bypass due to use of Ruby's `Resolv.getaddresses` method, which is OS-dependent and should not be relied upon for security measures, such as when used to blacklist private network addresses to prevent server-side request forgery.

O3 Security · Impact-Aware SCA

Is GHSA-hxhj-hp9m-qwc4 in your dependencies?

O3 detects GHSA-hxhj-hp9m-qwc4 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works