coreinfrastructure/best-practices-badge

Vulnerabilities

4 via 17 paths

Dependencies

189

Source

GitHub

Commit

42d12331

Find, fix and prevent vulnerabilities in your code.

Severity
  • 1
  • 2
  • 1
Status
  • 4
  • 0
  • 0

high severity

Cross-site Request Forgery (CSRF)

  • Vulnerable module: omniauth
  • Introduced through: omniauth-github@1.4.0 and omniauth-rails_csrf_protection@0.1.2

Detailed paths

  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b omniauth-github@1.4.0 omniauth@1.9.1
    Remediation: Upgrade to omniauth-github@2.0.0.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b omniauth-rails_csrf_protection@0.1.2 omniauth@1.9.1
    Remediation: Upgrade to omniauth-rails_csrf_protection@0.1.2.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b omniauth-github@1.4.0 omniauth-oauth2@1.7.1 omniauth@1.9.1
    Remediation: Upgrade to omniauth-github@1.4.0.

Overview

omniauth is a generalized Rack framework for multiple-provider authentication.

Affected versions of this package are vulnerable to Cross-site Request Forgery (CSRF). An attacker may be allowed to be connected to the user without the user's intent, interaction, or feedback. This permits a secondary account to be able to sign into the web application as the primary account.

Note:

  • The package is only vulnerable when used as part of the Ruby on Rails framework.
  • It is possible to use the omniauth-rails_csrf_protection gem to mitigate this attack

    Remediation

    Upgrade omniauth to version 2.0.0 or higher.

    References

medium severity

Information Exposure

  • Vulnerable module: actioncable
  • Introduced through: rails@6.1.3

Detailed paths

  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b rails@6.1.3 actioncable@6.1.3

Overview

actioncable is a package to structure many real-time application concerns into channels over a single WebSocket connection.

Affected versions of the package are vulnerable to Information Exposure. There is no way to filter out any sensitive data from the logs.

Remediation

There is no fix version for actioncable.

References

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: erubis
  • Introduced through: pronto-rails_best_practices@0.11.0

Detailed paths

  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b pronto-rails_best_practices@0.11.0 rails_best_practices@1.20.0 erubis@2.7.0

Overview

erubis is an implementation of eRuby and has the following features:

Affected versions of the package are vulnerable to Cross-site Scripting (XSS). Single quotes were not properly escaped in the helper.rb and helpers/rails_helper.rb files. The Erubis Documentation shows missing escaping.

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

ֿInjecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

There is no fix version for erubis.

References

low severity
new

Improper Input Validation

  • Vulnerable module: rexml
  • Introduced through: pronto@0.11.0, rubocop@0.91.1 and others

Detailed paths

  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b pronto@0.11.0 rexml@3.2.4
    Remediation: Upgrade to pronto@0.11.0.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b rubocop@0.91.1 rexml@3.2.4
    Remediation: Upgrade to rubocop@0.91.1.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b ruby-graphviz@1.2.5 rexml@3.2.4
    Remediation: Upgrade to ruby-graphviz@1.2.5.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b mdl@0.10.0 kramdown@2.3.1 rexml@3.2.4
    Remediation: Upgrade to mdl@0.10.0.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b pronto-eslint@0.11.0 pronto@0.11.0 rexml@3.2.4
    Remediation: Upgrade to pronto-eslint@0.11.0.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b pronto-rails_best_practices@0.11.0 pronto@0.11.0 rexml@3.2.4
    Remediation: Upgrade to pronto-rails_best_practices@0.11.0.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b pronto-rubocop@0.11.1 pronto@0.11.0 rexml@3.2.4
    Remediation: Upgrade to pronto-rubocop@0.11.1.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b pronto-rubocop@0.11.1 rubocop@0.91.1 rexml@3.2.4
    Remediation: Upgrade to pronto-rubocop@0.11.1.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b rubocop-performance@1.10.2 rubocop@0.91.1 rexml@3.2.4
    Remediation: Upgrade to rubocop-performance@1.10.2.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b rubocop-rails@2.8.0 rubocop@0.91.1 rexml@3.2.4
    Remediation: Upgrade to rubocop-rails@2.8.0.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b webmock@3.11.3 crack@0.4.5 rexml@3.2.4
    Remediation: Upgrade to webmock@3.11.3.
  • Introduced through: coreinfrastructure/best-practices-badge@coreinfrastructure/best-practices-badge#42d123313eb4318c69d4a649e1001d992033fe7b mdl@0.10.0 kramdown-parser-gfm@1.1.0 kramdown@2.3.1 rexml@3.2.4
    Remediation: Upgrade to mdl@0.10.0.

Overview

rexml is an An XML toolkit for Ruby.

Affected versions of this package are vulnerable to Improper Input Validation. When parsing and serializing a crafted XML document, REXML gem (including the one bundled with Ruby) can create a wrong XML document whose structure is different from the original one. The impact of this issue highly depends on context, but it may lead to a vulnerability in some programs that are using REXML.

Remediation

Upgrade rexml to version 3.2.5 or higher.

References