Skip to content

← Public intelligence

RubyGems package

rack-cors

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. UnratedRubyGemsPublished

    Rack CORS Middleware has Insecure File Permissions

    CVE-2024-27456 · GHSA-785g-282q-pwvx

    Affected
    • RubyGems rack-cors >= 2.0.1, <= 2.0.1
    Fixed in
    2.0.2· Vendor fix available
    Issue
    rack-cors (aka Rack CORS Middleware) 2.0.1 has 0666 permissions for the .rb files.

    Recommended action: Upgrade to 2.0.2 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 5.3RubyGemsPublished

    The rack-cors rubygem may allow directory traveral

    CVE-2019-18978 · GHSA-pf8f-w267-mq2h

    Affected
    • RubyGems rack-cors < 1.0.4
    Fixed in
    1.0.4· Vendor fix available
    Issue
    An issue was discovered in the rack-cors (aka Rack CORS Middleware) gem before 1.0.4 for Ruby. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format.

    Recommended action: Upgrade to 1.0.4 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. High, CVSS 8.8RubyGemsPublished

    Missing Regex anchor in Rack-Cors allows malicious third party site to perform CORS request

    CVE-2017-11173 · GHSA-2j9c-9vmv-7m39

    Affected
    • RubyGems rack-cors < 0.4.1
    Fixed in
    0.4.1· Vendor fix available
    Issue
    Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests. If the configuration were intended to allow only the trusted example.com domain name and not the malicious example.net domain name, then example.com.example.net (as well as example.com-example.net) would be inadvertently allowed.

    Recommended action: Upgrade to 0.4.1 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 →