CVE-2020-25739 — Vulnerability in gon — CVE Details
Gon gem lack of escaping certain input when outputting as JSON
Summary
Advisory Timeline
- First published April 30, 2021 (1991 days ago).
- Last revised February 19, 2024 — 1024 days after initial publication.
Remediation
Upgrade to the fixed version using your package manager.
gem install gon -v 6.4.0
After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.
Affected Packages (1)
Affects 1 ecosystem: rubygems (1).
| Package | Ecosystem | Affected | Fixed In |
|---|---|---|---|
| gon | rubygems | 0.1.0, 0.1.1, 0.2.0, 0.2.1 (+49 more) | 6.4.0 |
Vulnerability Classification
Common Weakness Enumeration (CWE) identifiers for this vulnerability type.
- CWE-79Cross-site Scripting (XSS)MITRE
CVSS Score Breakdown
What the CVSS (Common Vulnerability Scoring System) 6.1 score means for each attack dimension.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
References
- https://nvd.nist.gov/vuln/detail/CVE-2020-25739ADVISORY
- https://github.com/gazay/gon/commit/fe3c7b2191a992386dc9edd37de5447a4e809bc7WEB
- https://github.com/gazay/gonPACKAGE
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/gon/CVE-2020-25739.ymlWEB
- https://lists.debian.org/debian-lts-announce/2020/09/msg00018.htmlWEB
- https://usn.ubuntu.com/4560-1WEB
Frequently Asked Questions
- What is CVE-2020-25739?
- Gon gem lack of escaping certain input when outputting as JSON This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 6.1/10).
- How do I check if my project is affected by CVE-2020-25739?
- CVE-2020-25739 affects gon. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2020-25739 and 200,000+ other known vulnerabilities.
Severity & Exploitability
Exploitation requires specific conditions or has limited impact. Remediate within weeks.
Also Known As
Related CVEs
- CVE-2026-107715MEDIUM
Mechanize sends credential headers to another host after an HTTP redirect
- CVE-2026-107399MEDIUM
Mechanize sends credential headers to another origin after a meta refresh
Check if you're affected
Scan your dependencies to see if this vulnerability affects your projects.
Scan Your Dependencies