CVE-2013-0175

UnknownEPSS 3.73%

Last modified

CVE-2013-0175 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.73% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
3.73%

88.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
Erik Michaels-OberMulti Xml0.5.2
Grape ProjectGrape0.1.0
Grape ProjectGrape0.1.1
Grape ProjectGrape0.1.2
Grape ProjectGrape0.1.3
Grape ProjectGrape0.1.4
Grape ProjectGrape0.1.5
Grape ProjectGrape0.2.0
Grape ProjectGrape0.2.1
Grape ProjectGrape0.2.2
Grape ProjectGrape0.2.3
Grape ProjectGrape0.2.4
Grape ProjectGrape0.2.5

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2013-0175?
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.
How severe is CVE-2013-0175?
Severity scoring for CVE-2013-0175 is pending analysis. The EPSS model estimates a 3.73% probability of exploitation in the next 30 days.
How do I fix CVE-2013-0175?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2013-0175?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST