VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

ruby1.8: vulnerability history, versions and safety

ruby1.8 is a package in the Debian ecosystem. Vulert records 4 vulnerabilities for it across 5 releases, from Dec 2013 to Aug 2015. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded U4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ruby1.8 vulnerabilities

Vulert verdict on ruby1.8 i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 26 Aug 2015. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 4 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 26 Aug 2015 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for ruby1.8, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1.8.7.302-2 U4 Yes Details →
1.8.7.302-2squeeze4 U1 Yes Details →
1.8.7.302-2squeeze3 U2 Yes Details →
1.8.7.302-2squeeze2 U3 Yes Details →
1.8.7.302-2squeeze1 U4 Yes Details →

Newest 5 of 5 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 1
  • 2014 1
  • 2015 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for ruby1.8

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Vulnerability in ruby1.8 - security update N/A unrated 1.8.7.302-2squeeze4 18 May 2015
Vulnerability in ruby1.8 - Security Update N/A unrated 1.8.7.302-2squeeze3 21 Nov 2014
Vulnerability in ruby1.8 package N/A unrated 1.8.7.302-2squeeze2 04 Dec 2013
Security Update for ruby1.8 N/A unrated 1.8.7.302-2squeeze5 26 Aug 2015

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About ruby1.8

Is ruby1.8 safe to use?

Vulert records 4 vulnerabilities for ruby1.8 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 4 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does ruby1.8 have?

4 vulnerabilities are recorded for ruby1.8 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 4 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ruby1.8 vulnerabilities disclosed?

0 vulnerabilities were recorded for ruby1.8 in the last 12 months, and the oldest entry in this database dates to 04 Dec 2013. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of ruby1.8 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor ruby1.8 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ruby1.8 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.