Skip to content
Fencer Intel
high 7.5

CVE-2013-0175 json

Improper Input Validation in multi_xml

published 2013-04-25 13 y ago modified 2026-06-16 4 mo ago also GHSA-pchc-949f-53m5 , EUVD-2017-0282

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.7%
EPSS 3.7% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

multi_xml gem 0.5.2 for Ruby, as used in Grape before 0.2.6 and possibly other products, does not properly restrict casts of string values, which allows remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) involving nested XML entity references, by leveraging support for (1) YAML type conversion or (2) Symbol type conversion, a similar vulnerability to CVE-2013-0156.

Patch / fix

  • rubygems multi_xml 0.5.2
  • rubygem-multi_xml openSUSE Tumbleweed 0.6.0-1.31
  • rubygem-multi_xml openSUSE Tumbleweed 0.6.0-1.29
  • rubygem-multi_xml openSUSE Tumbleweed 0.6.0-1.27
  • ruby3.2-rubygem-multi_xml openSUSE Tumbleweed 0.6.0-1.23

opensuse advisories openSUSE-SU-2026:10355-1openSUSE-SU-2025:15122-1openSUSE-SU-2024:14173-1openSUSE-SU-2024:13164-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-0175 updated cvss 7.5

rubygem-multi_xml: Security flaw in Symbol and YAML parameters parsing

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.73% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
rubygems multi_xml
<0.5.2
0.5.2

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.