WordPress security changelog
MEDIUM CVE-2012-5371 Modified

Ruby: A security weakness

Ruby is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 5.0 CVSS · cve@mitre.org
NVD score 5.0 CVSS 2.0 · nvd@nist.gov
Component
Ruby
Plugin slug
ruby
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Nov 28, 2012
Weakness
CWE-310 — Cryptographic Issues

This CVE was published Nov 28, 2012 and is one of 1 known issue for this plugin.

What to do

Update, patch or deactivate.

Update Ruby to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

Ruby (aka CRuby) 1.9 before 1.9.3-p327 and 2.0 before r37575 computes hash values without properly restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table, as demonstrated by a universal multicollision attack against a variant of the MurmurHash2 algorithm, a different vulnerability than CVE-2011-4815.

NVD vector: AV:N/AC:L/Au:N/C:N/I:N/A:P

References

Primary and upstream sources