Skip to content

← Public intelligence

RubyGems package

geminabox

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.4RubyGemsPublished

    Gem in a Box vulnerable to Cross-site Scripting

    CVE-2017-14506 · GHSA-98hq-3qvg-pg78

    Affected
    • RubyGems geminabox < 0.13.6
    Fixed in
    0.13.6· Vendor fix available
    Issue
    geminabox (aka Gem in a Box) before 0.13.6 is vulnerable to Cross-site Scripting (XSS), as demonstrated by uploading a gem file that has a crafted gem.homepage value in its .gemspec file.

    Recommended action: Upgrade to 0.13.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 8.8RubyGemsPublished

    Gem in a Box vulnerable to Cross-site Request Forgery

    CVE-2017-14683 · GHSA-qwv2-2x8g-g43g

    Affected
    • RubyGems geminabox < 0.13.7
    Fixed in
    0.13.7· Vendor fix available
    Issue
    geminabox (aka Gem in a Box) before 0.13.7 has CSRF, as demonstrated by an unintended gem upload.

    Recommended action: Upgrade to 0.13.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Medium, CVSS 6.1RubyGemsPublished

    Geminabox contains Cross-site Scripting

    CVE-2017-16792 · GHSA-653m-r33x-39ff

    Affected
    • RubyGems geminabox < 0.13.10
    Fixed in
    0.13.10· Vendor fix available
    Issue
    Stored cross-site scripting (XSS) vulnerability in "geminabox" (Gem in a Box) before 0.13.10 allows attackers to inject arbitrary web script via the "homepage" value of a ".gemspec" file, related to views/gem.erb and views/index.erb.

    Recommended action: Upgrade to 0.13.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →