How severe is GHSA-r23g-3qw4-gfh2?

No CVSS score has been assigned to GHSA-r23g-3qw4-gfh2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r23g-3qw4-gfh2?

GHSA-r23g-3qw4-gfh2 affects the following packages: RedCloth (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-r23g-3qw4-gfh2?

Update RedCloth to 4.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r23g-3qw4-gfh2 is resolved across your whole dependency graph.

How do I detect GHSA-r23g-3qw4-gfh2 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for RedCloth. 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-r23g-3qw4-gfh2 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-r23g-3qw4-gfh2?

O3 pinpoints whether GHSA-r23g-3qw4-gfh2 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-r23g-3qw4-gfh2 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-r23g-3qw4-gfh2, 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-r23g-3qw4-gfh2?

GHSA-r23g-3qw4-gfh2 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-r23g-3qw4-gfh2 published, and has it been updated?

GHSA-r23g-3qw4-gfh2 was published on October 24, 2017 and was last updated on December 3, 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-r23g-3qw4-gfh2

GHSA-r23g-3qw4-gfh2 is a Cross-site Scripting (XSS) vulnerability in RedCloth. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-r23g-3qw4-gfh2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

RedCloth Cross-site Scripting vulnerability

Also known asCVE-2012-6684

Published

Oct 24, 2017

Updated

Dec 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Dec 3, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

💎RedCloth

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

Cross-site scripting (XSS) vulnerability in the RedCloth library 4.2.9 for Ruby and earlier allows remote attackers to inject arbitrary web script or HTML via a javascript: URI.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`RedCloth`	all versions	4.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.

Cross-site scripting (XSS) vulnerability in the RedCloth library 4.2.9 f…

seclists.orgNVDSep 2016

Detection & mitigation playbook

Open-source dependency

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

Frequently Asked Questions

Cross-site scripting (XSS) vulnerability in the RedCloth library 4.2.9 for Ruby and earlier allows remote attackers to inject arbitrary web script or HTML via a `javascript:` URI.

O3 Security · Impact-Aware SCA

Is GHSA-r23g-3qw4-gfh2 in your dependencies?

O3 detects GHSA-r23g-3qw4-gfh2 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