Is crack 0.1 vulnerable?

RubyGems · 8 releases from 0.1.1 to 0.1.8 · latest crack is 1.0.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. crack 0.1.8, the last 0.1 release, is affected by 1 known security advisory (1 high), including CVE-2013-1800. Upgrade to 0.3.2 or later to fix all of them.

Upgrade with:bundle update --conservative crack # Gemfile: '>= 0.3.2'

Is your project on an affected crack?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting crack 0.1.8

  • HighCVE-2013-1800GHSA-m7fq-cf8q-35q724 Oct 2017

    crack does not properly restrict casts of string values

    Affected
    <0.3.2
    Fixed in
    0.3.2

Every crack 0.1.x release

Affected: 0.1.1 to 0.1.8. Latest crack: 1.0.1.

VersionKnown advisories
crack 0.1.8CVE-2013-1800
crack 0.1.7CVE-2013-1800
crack 0.1.6CVE-2013-1800
crack 0.1.5CVE-2013-1800
crack 0.1.4CVE-2013-1800
crack 0.1.3CVE-2013-1800
crack 0.1.2CVE-2013-1800
crack 0.1.1CVE-2013-1800

Which of your client projects are still on crack 0.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact crack version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other crack versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.