CVE-2008-3655

UnknownEPSS 14.09%

Last modified

CVE-2008-3655 is a vulnerability of currently unknown severity. Ruby 1.8.5 and earlier, 1.8.6 through 1.8.6-p286, 1.8.7 through 1.8.7-p71, and 1.9 through r18423 does not properly restrict access to critical variables and methods at various safe levels, which allows context-dependent attackers to bypass intended access restrictions via (1) untrace_var, (2) $PROGRAM_NAME, and (3) syslog at safe level 4, and (4) insecure methods at safe levels 1 through 3.. EPSS estimates a 14.09% chance of exploitation in the next 30 days.

Description

Ruby 1.8.5 and earlier, 1.8.6 through 1.8.6-p286, 1.8.7 through 1.8.7-p71, and 1.9 through r18423 does not properly restrict access to critical variables and methods at various safe levels, which allows context-dependent attackers to bypass intended access restrictions via (1) untrace_var, (2) $PROGRAM_NAME, and (3) syslog at safe level 4, and (4) insecure methods at safe levels 1 through 3.

Metrics

EPSS Probability
14.09%

96.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
Ruby-LangRuby<= 1.8.5
Ruby-LangRuby1.6.8
Ruby-LangRuby1.8.0
Ruby-LangRuby1.8.1
Ruby-LangRuby1.8.2
Ruby-LangRuby1.8.3
Ruby-LangRuby1.8.4
Ruby-LangRuby1.8.5P11
Ruby-LangRuby1.8.6
Ruby-LangRuby1.8.7
Ruby-LangRuby1.9.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2008-3655?
Ruby 1.8.5 and earlier, 1.8.6 through 1.8.6-p286, 1.8.7 through 1.8.7-p71, and 1.9 through r18423 does not properly restrict access to critical variables and methods at various safe levels, which allows context-dependent attackers to bypass intended access restrictions via (1) untrace_var, (2) $PROGRAM_NAME, and (3) syslog at safe level 4, and (4) insecure methods at safe levels 1 through 3.
How severe is CVE-2008-3655?
Severity scoring for CVE-2008-3655 is pending analysis. The EPSS model estimates a 14.09% probability of exploitation in the next 30 days.
How do I fix CVE-2008-3655?
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-2008-3655?

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

Scan your code now

Source: NVD / NIST