How severe is CVE-2013-0162?

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

Which packages are affected by CVE-2013-0162?

CVE-2013-0162 affects the following packages: ruby_parser (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-0162?

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

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

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

How do I mitigate CVE-2013-0162 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.

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

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

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

CVE-2013-0162 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-0162 published, and has it been updated?

CVE-2013-0162 was published on May 5, 2022 and was last updated on November 29, 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-0162 — ruby_parser

Fix: seattlerb/ruby_parser@506c7e1

CVE-2013-0162 is a CWE-264 vulnerability in ruby_parser. A fix is available for ruby_parser — see the affected versions and patch details below.

ruby_parser allows local users to overwrite arbitrary files via symlink attack on temporary file with predictable name

Published

May 5, 2022

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

💎ruby_parser

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 diff_pp function in lib/gauntlet_rubyparser.rb in the ruby_parser gem 3.1.1 and earlier for Ruby allows local users to overwrite arbitrary files via a symlink attack on a temporary file with a predictable name in /tmp.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`ruby_parser`	≥ 2.0.2&&< 3.1.2	3.1.2`bundle update ruby_parser --conservative`

Affected Products

1 product · 29 configurations

Application

ruby parserryan_davis

≤ 3.1.1

28 versions

1.0.02.0.02.0.12.0.22.0.32.0.42.0.52.0.62.1.02.2.02.3.02.3.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ruby_parser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ruby_parser to 3.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-0162 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.

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 HatLow

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	`apache-commons-codec-0:1.7-2.el6_3`	RHSA-2013:0544
RHEL 6 Version of OpenShift Enterprise	`graphviz-0:2.26.0-10.el6`	RHSA-2013:0582

Frequently Asked Questions

The `diff_pp` function in `lib/gauntlet_rubyparser.rb` in the ruby_parser gem 3.1.1 and earlier for Ruby allows local users to overwrite arbitrary files via a symlink attack on a temporary file with a predictable name in `/tmp`.

O3 Security · Impact-Aware SCA

Is CVE-2013-0162 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works