How severe is GHSA-jphg-qwrw-7w9g?

GHSA-jphg-qwrw-7w9g has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jphg-qwrw-7w9g?

GHSA-jphg-qwrw-7w9g affects the following packages: json (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-jphg-qwrw-7w9g?

Update json to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jphg-qwrw-7w9g is resolved across your whole dependency graph.

How do I detect GHSA-jphg-qwrw-7w9g in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for json. 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-jphg-qwrw-7w9g 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-jphg-qwrw-7w9g?

O3 pinpoints whether GHSA-jphg-qwrw-7w9g 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-jphg-qwrw-7w9g actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-jphg-qwrw-7w9g, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-jphg-qwrw-7w9g?

GHSA-jphg-qwrw-7w9g is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jphg-qwrw-7w9g published, and has it been updated?

GHSA-jphg-qwrw-7w9g was published on July 27, 2020 and was last updated on March 8, 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

GHSA-jphg-qwrw-7w9g

HIGH

GHSA-jphg-qwrw-7w9g is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in json. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-jphg-qwrw-7w9g is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Unsafe object creation in json RubyGem

Also known asCVE-2020-10663

Published

Jul 27, 2020

Updated

Mar 8, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Blast Radius

1 pkg affected

💎json

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 JSON gem through 2.2.0 for Ruby, as used in Ruby 2.4 through 2.4.9, 2.5 through 2.5.7, and 2.6 through 2.6.5, has an Unsafe Object Creation Vulnerability. This is quite similar to CVE-2013-0269/GHSA-x457-cw4h-hq5f, but does not rely on poor garbage-collection behavior within Ruby. Specifically, use of JSON parsing methods can lead to creation of a malicious object within the interpreter, with adverse effects that are application-dependent.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`json`	all versions	2.3.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The JSON gem through 2.2.0 for Ruby, as used in Ruby 2.4 through 2.4.9, …

github.comGithubMar 2020

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for json. 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 json to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jphg-qwrw-7w9g 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-jphg-qwrw-7w9g 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-jphg-qwrw-7w9g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-jphg-qwrw-7w9g in your dependencies?

O3 detects GHSA-jphg-qwrw-7w9g 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