BundlerApplication
CVE-2013-0334
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBundler before 1.7, when multiple top-level source lines are used, allows remote attackers to install arbitrary gems by creating a gem with the same name as another gem in a different source.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBundler before version 1.7 has a vulnerability in gem source resolution when multiple top-level sources are configured. An attacker can publish a malicious gem with the same name as a legitimate gem from another source, causing Bundler to install the attacker's gem instead of the intended one.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
BundlerApplication
< 1.7.0
FedoraOperating system
= 19= 20= 21= 13.1= 13.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Bundler versionRun `bundler --version` or `gem list bundler` to see the installed version numberAffected if Version is less than 1.7.0 (for example, 1.6.x, 1.5.x, etc.)
-
Identify configured gem sources in GemfileInspect the Gemfile in the project root for multiple `source` declarations at the top level, such as multiple lines starting with `source 'https://rubygems.org'` pointing to different registriesAffected if Two or more top-level source declarations are present pointing to different gem repositories
-
Check global gem sources configurationInspect `~/.gemrc` or run `gem sources -l` to list all configured gem sourcesAffected if Multiple gem sources are configured, especially including sources other than the official RubyGems.org
-
Verify gem source priority behaviorCreate a test Gemfile with a gem name that exists in multiple configured sources, then run `bundle install` and inspect which source the gem is fetched from using `bundle show <gemname>` or verbose outputAffected if Bundler resolves gems from a source other than the intended/pinned source when multiple sources exist
You are affected if Bundler version is below 1.7.0 AND you have multiple gem sources configured in your Gemfile or globally, as this creates the conditions for source confusion during gem resolution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.7.0
Upgrade Bundler to version 1.7 or later. Additionally, pin gem sources explicitly and verify gem integrity before installation.
Fix this in Bundler
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-0334 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data