How severe is CVE-2013-0256?

No CVSS score has been assigned to CVE-2013-0256 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-0256?

CVE-2013-0256 affects the following packages: rdoc (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-0256?

Update rdoc to 3.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-0256 is resolved across your whole dependency graph.

How do I detect CVE-2013-0256 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rdoc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-0256 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2013-0256 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-0256 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 CVE-2013-0256?

CVE-2013-0256 has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 87th 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 CVE-2013-0256?

CVE-2013-0256 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 CVE-2013-0256 published, and has it been updated?

CVE-2013-0256 was published on October 24, 2017 and was last updated on December 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

Not in CISA KEV

CVE-2013-0256 — rdoc

Fix: rdoc/rdoc@ffa8788

CVE-2013-0256 is a Cross-site Scripting (XSS) vulnerability in rdoc. A fix is available for rdoc — see the affected versions and patch details below.

RDoc contains XSS vulnerability

Published

Oct 24, 2017

Updated

Dec 8, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

💎rdoc

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

darkfish.js in RDoc 2.3.0 through 3.12 and 4.x before 4.0.0.preview2.1, as used in Ruby, does not properly generate documents, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted URL.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`rdoc`	≥ 2.3.0&&< 3.12.1	3.12.1`bundle update rdoc --conservative`

Affected Products

3 products · 17 configurations

ubuntu linuxcanonical

2 versions

12.0412.10

Application

rdocruby-lang

≥ 2.3.0 && < 3.12

1 version

4.0.0

Application

rubyruby-lang

6 versions

1.91.9.11.9.21.9.32.02.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rdoc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rdoc to 3.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-0256 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
CloudForms for RHEL 6	`rubygem-activesupport-1:3.0.10-10.el6cf`	RHSA-2013:0548
Red Hat Subscription Asset Manager 1.2	`candlepin-0:0.7.24-1.el6_3`	RHSA-2013:0686
RHEL 6 Version of OpenShift Enterprise	`ruby193-ruby-0:1.9.3.327-28.el6`	RHSA-2013:0701
RHEL 6 Version of OpenShift Enterprise	`ruby193-rubygem-activesupport-1:3.2.8-4.el6`	RHSA-2013:0728

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-0256 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works