bundler-audit 0.7.0.1 → 0.9.0

data/data/ruby-advisory-db/gems/puma/CVE-2020-11077.yml

@@ -1,31 +0,0 @@
----
-gem: puma
-cve: 2020-11077
-ghsa: w64w-qqph-5gxm
-url: https://github.com/puma/puma/security/advisories/GHSA-w64w-qqph-5gxm
-date: 2020-05-22
-title: HTTP Smuggling via Transfer-Encoding Header in Puma
-description: |-
-  ### Impact
-
-  This is a similar but different vulnerability to the one patched in 3.12.5 and 4.3.4.
-
-  A client could smuggle a request through a proxy, causing the proxy to send a response
-  back to another unknown client.
-
-  If the proxy uses persistent connections and the client adds another request in via HTTP
-  pipelining, the proxy may mistake it as the first request's body. Puma, however,
-  would see it as two requests, and when processing the second request, send back
-  a response that the proxy does not expect. If the proxy has reused the persistent
-  connection to Puma to send another request for a different client, the second response
-  from the first client will be sent to the second client.
-
-  ### Patches
-
-  The problem has been fixed in Puma 3.12.6 and Puma 4.3.5.
-
-cvss_v3: 6.8
-
-patched_versions:
-- "~> 3.12.6"
-- ">= 4.3.5"

data/data/ruby-advisory-db/gems/puma/CVE-2020-5247.yml

@@ -1,25 +0,0 @@
----
-gem: puma
-cve: 2020-5247
-ghsa: 84j7-475p-hp8v
-url: https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8v
-date: 2020-02-27
-title: HTTP Response Splitting vulnerability in puma
-description: |-
-  If an application using Puma allows untrusted input in a response header,
-  an attacker can use newline characters (i.e. CR, LF) to end the header and
-  inject malicious content, such as additional headers or an entirely new
-  response body. This vulnerability is known as HTTP Response Splitting.
-
-  While not an attack in itself, response splitting is a vector for several
-  other attacks, such as cross-site scripting (XSS).
-
-cvss_v3: 6.5
-
-patched_versions:
-  - "~> 3.12.4"
-  - ">= 4.3.3"
-
-related:
-  cve:
-    - 2019-16254

data/data/ruby-advisory-db/gems/puma/CVE-2020-5249.yml

@@ -1,36 +0,0 @@
----
-gem: puma
-cve: 2020-5249
-ghsa: 33vf-4xgg-9r58
-url: https://github.com/puma/puma/security/advisories/GHSA-33vf-4xgg-9r58
-date: 2020-03-03
-title: HTTP Response Splitting (Early Hints) in Puma
-description: |-
-  ### Impact
-  If an application using Puma allows untrusted input in an early-hints header,
-  an attacker can use a carriage return character to end the header and inject
-  malicious content, such as additional headers or an entirely new response body.
-  This vulnerability is known as [HTTP Response
-  Splitting](https://owasp.org/www-community/attacks/HTTP_Response_Splitting)
-
-  While not an attack in itself, response splitting is a vector for several other
-  attacks, such as cross-site scripting (XSS).
-
-  This is related to [CVE-2020-5247](https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8v),
-  which fixed this vulnerability but only for regular responses.
-
-  ### Patches
-  This has been fixed in 4.3.3 and 3.12.4.
-
-  ### Workarounds
-  Users can not allow untrusted/user input in the Early Hints response header.
-
-cvss_v3: 6.5
-
-patched_versions:
-  - "~> 3.12.4"
-  - ">= 4.3.3"
-
-related:
-  cve:
-    - 2020-5247

data/data/ruby-advisory-db/gems/quick_magick/OSVDB-106954.yml

@@ -1,7 +0,0 @@
----
-gem: quick_magick
-osvdb: 106954
-url: http://osvdb.org/show/osvdb/106954
-title: quick_magick Gem for Ruby QuickMagick::Image.read Function Crafted String Handling Remote Command Injection 
-date: 2011-01-12
-description: quick_magick Gem for Ruby contains a flaw in the QuickMagick::Image.read function. The issue is triggered when handling a specially crafted string. This may allow a remote attacker to inject arbitrary commands.

data/data/ruby-advisory-db/gems/rack/CVE-2011-5036.yml

@@ -1,21 +0,0 @@
----
-gem: rack
-cve: 2011-5036
-osvdb: 78121
-url: https://nvd.nist.gov/vuln/detail/CVE-2011-5036
-title: |
-  Rack Hash Collision Form Parameter Parsing Remote DoS
-date: 2011-12-28
-
-description: |
-  Rack contains a flaw that may allow a remote denial of service. The issue is
-  triggered when an attacker sends multiple crafted parameters which trigger
-  hash collisions, and will result in loss of availability for the program via
-  CPU consumption.
-
-cvss_v2: 5.0
-patched_versions:
-  - "~> 1.1.3"
-  - "~> 1.2.5"
-  - "~> 1.3.6"
-  - ">= 1.4.0"

data/data/ruby-advisory-db/gems/rack/CVE-2012-6109.yml

@@ -1,21 +0,0 @@
----
-gem: rack
-cve: 2012-6109
-osvdb: 89317
-url: https://nvd.nist.gov/vuln/detail/CVE-2012-6109
-title: |
-  Rack Regular Expressions Engine Content-Disposition Header Parsing Infinite Loop Remote DoS
-date: 2012-05-04
-
-description: |
-  Rack contains a flaw in the Regular Expressions Engine that may allow a remote
-  denial of service. The issue is triggered when parsing context-disposition
-  headers. With a specially crafted header, a remote attacker can cause an
-  infinite loop, which will result in a loss of availability for the webserver.
-
-cvss_v2: 4.3
-patched_versions:
-  - "~> 1.1.4"
-  - "~> 1.2.6"
-  - "~> 1.3.7"
-  - ">= 1.4.2"

data/data/ruby-advisory-db/gems/rack/CVE-2013-0183.yml

@@ -1,19 +0,0 @@
----
-gem: rack
-cve: 2013-0183
-osvdb: 89320
-url: https://nvd.nist.gov/vuln/detail/CVE-2013-0183
-title: |
-  Rack Long String Parsing Memory Consumption Remote DoS
-date: 2013-01-07
-
-description: |
-  Rack contains a flaw that may allow a remote denial of service. The issue is
-  triggered when parsing an overly long string. With a specially crafted string,
-  a remote attacker can cause a consumption of memory. This will result in a
-  loss of availability for the webserver.
-
-cvss_v2: 5.0
-patched_versions:
-  - "~> 1.3.8"
-  - ">= 1.4.3"

data/data/ruby-advisory-db/gems/rack/CVE-2013-0184.yml

@@ -1,20 +0,0 @@
----
-gem: rack
-cve: 2013-0184
-osvdb: 89327
-url: https://nvd.nist.gov/vuln/detail/CVE-2013-0184
-title: |
-  Rack Rack::Auth::AbstractRequest Class Unspecified Remote DoS
-date: 2013-01-13
-
-description: |
-  Rack contains a flaw in the Rack::Auth::AbstractRequest class that may allow
-  a remote denial of service. The issue is triggered when an unspecified error
-  occurs, which will result in a loss of availability for the webserver.
-
-cvss_v2: 4.3
-patched_versions:
-  - "~> 1.1.5"
-  - "~> 1.2.7"
-  - "~> 1.3.9"
-  - ">= 1.4.4"

data/data/ruby-advisory-db/gems/rack/CVE-2013-0262.yml

@@ -1,18 +0,0 @@
----
-gem: rack
-cve: 2013-0262
-osvdb: 89938
-url: https://nvd.nist.gov/vuln/detail/CVE-2013-0262
-title: |
-  Rack Rack::File Function Symlink Traversal Arbitrary File Disclosure
-date: 2013-02-07
-
-description: |
-  Rack contains a flaw as the Rack::File function creates temporary files
-  insecurely. It is possible for a local attacker to use a symlink attack to
-  traverse to an arbitrary file and disclose its contents
-
-cvss_v2: 4.3
-patched_versions:
-- "~> 1.4.5"
-- ">= 1.5.2"

data/data/ruby-advisory-db/gems/rack/CVE-2013-0263.yml

@@ -1,23 +0,0 @@
----
-gem: rack
-cve: 2013-0263
-osvdb: 89939
-url: https://nvd.nist.gov/vuln/detail/CVE-2013-0263
-title: |
-  Rack Rack::Session::Cookie Function Timing Attack Remote Code Execution
-date: 2013-02-07
-
-description: |
-  Rack contains a flaw that is due to an error in the Rack::Session::Cookie
-  function. Users of the Marshal session cookie encoding (the default), are
-  subject to a timing attack that may lead an attacker to execute arbitrary
-  code. This attack is more practical against 'cloud' users as intra-cloud
-  latencies are sufficiently low to make the attack viable.
-
-cvss_v2: 5.1
-patched_versions:
-  - ~> 1.1.6
-  - ~> 1.2.8
-  - ~> 1.3.10
-  - ~> 1.4.5
-  - ">= 1.5.2"

data/data/ruby-advisory-db/gems/rack/CVE-2015-3225.yml

@@ -1,18 +0,0 @@
----
-gem: rack
-cve: 2015-3225
-url: https://groups.google.com/forum/#!topic/ruby-security-ann/gcUbICUmKMc
-title: |
-  Potential Denial of Service Vulnerability in Rack
-date: 2015-06-16
-
-description: |
-  Carefully crafted requests can cause a `SystemStackError` and potentially 
-  cause a denial of service attack. 
-
-  All users running an affected release should upgrade. 
-
-patched_versions:
-  - ">= 1.6.2"
-  - "~> 1.5.4"
-  - "~> 1.4.6"

data/data/ruby-advisory-db/gems/rack/CVE-2018-16470.yml

@@ -1,56 +0,0 @@
----
-gem: rack
-cve: 2018-16470
-url: https://groups.google.com/forum/#!topic/ruby-security-ann/Dz4sRl-ktKk
-title: Possible DoS vulnerability in Rack
-date: 2018-11-05
-
-description: |
-  There is a possible DoS vulnerability in the multipart parser in Rack. This
-  vulnerability has been assigned the CVE identifier CVE-2018-16470.
-
-  Versions Affected:  2.0.4, 2.0.5
-  Not affected:       <= 2.0.3
-  Fixed Versions:     2.0.6
-
-  Impact
-  ------
-  There is a possible DoS vulnerability in the multipart parser in Rack.
-  Carefully crafted requests can cause the multipart parser to enter a
-  pathological state, causing the parser to use CPU resources disproportionate to
-  the request size.
-
-  Impacted code can look something like this:
-
-  ```
-  Rack::Request.new(env).params
-  ```
-
-  But any code that uses the multi-part parser may be vulnerable.
-
-  Rack users that have manually adjusted the buffer size in the multipart parser
-  may be vulnerable as well.
-
-  All users running an affected release should either upgrade or use one of the
-  workarounds immediately.
-
-  Releases
-  --------
-  The 2.0.6 release is available at the normal locations.
-
-  Workarounds
-  -----------
-  To work around this issue, the following code can be used:
-
-  ```
-  require "rack/multipart/parser"
-
-  Rack::Multipart::Parser.send :remove_const, :BUFSIZE
-  Rack::Multipart::Parser.const_set :BUFSIZE, 16384
-  ```
-
-unaffected_versions:
-  - "<= 2.0.3"
-
-patched_versions:
-  - ">= 2.0.6"

data/data/ruby-advisory-db/gems/rack/CVE-2018-16471.yml

@@ -1,80 +0,0 @@
----
-gem: rack
-cve: 2018-16471
-url: https://groups.google.com/forum/#!topic/ruby-security-ann/NAalCee8n6o
-title: Possible XSS vulnerability in Rack
-date: 2018-11-05
-
-description: |
-  There is a possible vulnerability in Rack. This vulnerability has been
-  assigned the CVE identifier CVE-2018-16471.
-
-  Versions Affected:  All.
-  Not affected:       None.
-  Fixed Versions:     2.0.6, 1.6.11
-
-  Impact
-  ------
-  There is a possible XSS vulnerability in Rack.  Carefully crafted requests can
-  impact the data returned by the `scheme` method on `Rack::Request`.
-  Applications that expect the scheme to be limited to "http" or "https" and do
-  not escape the return value could be vulnerable to an XSS attack.
-
-  Vulnerable code looks something like this:
-
-  ```
-  <%= request.scheme.html_safe %>
-  ```
-
-  Note that applications using the normal escaping mechanisms provided by Rails
-  may not impacted, but applications that bypass the escaping mechanisms, or do
-  not use them may be vulnerable.
-
-  All users running an affected release should either upgrade or use one of the
-  workarounds immediately.
-
-  Releases
-  --------
-  The 2.0.6 and 1.6.11 releases are available at the normal locations.
-
-  Workarounds
-  -----------
-  The following monkey patch can be applied to work around this issue:
-
-  ```
-  require "rack"
-  require "rack/request"
-
-  class Rack::Request
-  SCHEME_WHITELIST = %w(https http).freeze
-
-  def scheme
-    if get_header(Rack::HTTPS) == 'on'
-      'https'
-    elsif get_header(HTTP_X_FORWARDED_SSL) == 'on'
-      'https'
-    elsif forwarded_scheme
-      forwarded_scheme
-    else
-      get_header(Rack::RACK_URL_SCHEME)
-    end
-  end
-
-  def forwarded_scheme
-    scheme_headers = [
-      get_header(HTTP_X_FORWARDED_SCHEME),
-      get_header(HTTP_X_FORWARDED_PROTO).to_s.split(',')[0]
-    ]
-
-    scheme_headers.each do |header|
-      return header if SCHEME_WHITELIST.include?(header)
-    end
-
-    nil
-  end
-  end
-  ```
-
-patched_versions:
-  - "~> 1.6.11"
-  - ">= 2.0.6"

data/data/ruby-advisory-db/gems/rack/CVE-2019-16782.yml

@@ -1,32 +0,0 @@
----
-gem: rack
-cve: 2019-16782
-ghsa: hrqr-hxpp-chr3
-url: https://github.com/rack/rack/security/advisories/GHSA-hrqr-hxpp-chr3
-date: 2019-12-18
-title: Possible information leak / session hijack vulnerability
-description: |-
-  There's a possible information leak / session hijack vulnerability in Rack.
-
-  Attackers may be able to find and hijack sessions by using timing attacks
-  targeting the session id. Session ids are usually stored and indexed in a
-  database that uses some kind of scheme for speeding up lookups of that
-  session id. By carefully measuring the amount of time it takes to look up
-  a session, an attacker may be able to find a valid session id and hijack
-  the session.
-
-  The session id itself may be generated randomly, but the way the session is
-  indexed by the backing store does not use a secure comparison.
-
-  Impact:
-
-  The session id stored in a cookie is the same id that is used when querying
-  the backing session storage engine.  Most storage mechanisms (for example a
-  database) use some sort of indexing in order to speed up the lookup of that
-  id.  By carefully timing requests and session lookup failures, an attacker
-  may be able to perform a timing attack to determine an existing session id
-  and hijack that session.
-
-patched_versions:
-  - "~> 1.6.12"
-  - ">= 2.0.8"

data/data/ruby-advisory-db/gems/rack/CVE-2020-8161.yml

@@ -1,32 +0,0 @@
----
-gem: rack
-cve: 2020-8161
-url: https://groups.google.com/forum/#!topic/ruby-security-ann/T4ZIsfRf2eA
-date: 2020-05-12
-title: Directory traversal in Rack::Directory app bundled with Rack
-description: |
-  There was a possible directory traversal vulnerability in the Rack::Directory app
-  that is bundled with Rack.
-
-  Versions Affected:  rack < 2.2.0
-  Not affected:       Applications that do not use Rack::Directory.
-  Fixed Versions:     2.1.3, >= 2.2.0
-
-  Impact
-  ------
-
-  If certain directories exist in a director that is managed by
-  `Rack::Directory`, an attacker could, using this vulnerability, read the
-  contents of files on the server that were outside of the root specified in the
-  Rack::Directory initializer.
-
-  Workarounds
-  -----------
-
-  Until such time as the patch is applied or their Rack version is upgraded,
-  we recommend that developers do not use Rack::Directory in their
-  applications.
-
-patched_versions:
-  - "~> 2.1.3"
-  - ">= 2.2.0"