Skip to content

← Public intelligence

RubyGems package

twitter-bootstrap-rails

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

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

  1. UnratedRubyGemsPublished

    Reflective Cross-site Scripting Vulnerability in twitter-bootstrap-rails

    CVE-2014-4920 · GHSA-vpqv-mqvc-pcx2

    Affected
    • RubyGems twitter-bootstrap-rails < 3.2.0
    Fixed in
    3.2.0· Vendor fix available
    Issue
    The twitter-bootstrap-rails Gem for Rails contains a flaw that enables a reflected cross-site scripting (XSS) attack. This flaw exists because the bootstrapflash helper method does not validate input when handling flash messages before returning it to users. This may allow a context-dependent attacker to create a specially crafted request that would execute arbitrary script code in a user's browser session within the trust relationship between their browser and the server.

    Recommended action: Upgrade to 3.2.0 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. Medium, CVSS 6.1RubyGemsAmendedPublished

    Bootstrap Vulnerable to Cross-Site Scripting

    CVE-2019-8331 · GHSA-9v3m-8fp8-mj99

    Affected
    • RubyGems twitter-bootstrap-rails < 5.3.0
    Fixed in
    5.3.0· Vendor fix available
    Issue
    Versions of bootstrap prior to 3.4.1 for 3.x and 4.3.1 for 4.x are vulnerable to Cross-Site Scripting (XSS). The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript. Recommendation For bootstrap 4.x upgrade to 4.3.1 or later. For bootstrap 3.x upgrade to 3.4.1 or later.

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

    Sources:osv.dev (1)github.com (2)Source checked Evidence →