Vulnerabilities

4 via 7 paths

Dependencies

32

Source

GitHub

Commit

20eb9c91

Find, fix and prevent vulnerabilities in your code.

Severity
  • 1
  • 3
Status
  • 4
  • 0
  • 0

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: addressable
  • Introduced through: metadata-json-lint@2.2.0

Detailed paths

  • Introduced through: shinesolutions/puppet-amazon-ssm-agent@shinesolutions/puppet-amazon-ssm-agent#20eb9c91ca4a41346980f079d0b5f136a3842d0e metadata-json-lint@2.2.0 json-schema@2.8.1 addressable@2.7.0
    Remediation: Upgrade to metadata-json-lint@2.2.0.

Overview

addressable is an is an alternative implementation to the URI implementation that is part of Ruby's standard library.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) within the URI template implementation. A maliciously crafted template may result in uncontrolled resource consumption.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade addressable to version 2.8.0 or higher.

References

medium severity

Improper Input Validation

  • Vulnerable module: puppet
  • Introduced through: puppet@5.5.6 and puppetlabs_spec_helper@2.14.1

Detailed paths

  • Introduced through: shinesolutions/puppet-amazon-ssm-agent@shinesolutions/puppet-amazon-ssm-agent#20eb9c91ca4a41346980f079d0b5f136a3842d0e puppet@5.5.6
    Remediation: Upgrade to puppet@6.13.0.
  • Introduced through: shinesolutions/puppet-amazon-ssm-agent@shinesolutions/puppet-amazon-ssm-agent#20eb9c91ca4a41346980f079d0b5f136a3842d0e puppetlabs_spec_helper@2.14.1 puppet-syntax@2.6.1 puppet@5.5.6
    Remediation: Upgrade to puppetlabs_spec_helper@2.14.1.

Overview

puppet is an automated configuration management tool.

Affected versions of this package are vulnerable to Improper Input Validation. Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node's catalog falls back to the default node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting strict_hostname_checking = true in puppet.conf on your Puppet master.

Remediation

Upgrade puppet to version 6.13.0 or higher.

References

medium severity

Information Disclosure

  • Vulnerable module: puppet
  • Introduced through: puppet@5.5.6 and puppetlabs_spec_helper@2.14.1

Detailed paths

  • Introduced through: shinesolutions/puppet-amazon-ssm-agent@shinesolutions/puppet-amazon-ssm-agent#20eb9c91ca4a41346980f079d0b5f136a3842d0e puppet@5.5.6
    Remediation: Upgrade to puppet@6.25.1.
  • Introduced through: shinesolutions/puppet-amazon-ssm-agent@shinesolutions/puppet-amazon-ssm-agent#20eb9c91ca4a41346980f079d0b5f136a3842d0e puppetlabs_spec_helper@2.14.1 puppet-syntax@2.6.1 puppet@5.5.6
    Remediation: Upgrade to puppetlabs_spec_helper@2.14.1.

Overview

puppet is an automated configuration management tool.

Affected versions of this package are vulnerable to Information Disclosure that may result in a leak of HTTP credentials.

Remediation

Upgrade puppet to version 6.25.1, 7.12.1 or higher.

References

medium severity

Denial of Service (DoS)

  • Vulnerable module: puppet
  • Introduced through: puppet@5.5.6 and puppetlabs_spec_helper@2.14.1

Detailed paths

  • Introduced through: shinesolutions/puppet-amazon-ssm-agent@shinesolutions/puppet-amazon-ssm-agent#20eb9c91ca4a41346980f079d0b5f136a3842d0e puppet@5.5.6
    Remediation: Upgrade to puppet@6.25.1.
  • Introduced through: shinesolutions/puppet-amazon-ssm-agent@shinesolutions/puppet-amazon-ssm-agent#20eb9c91ca4a41346980f079d0b5f136a3842d0e puppetlabs_spec_helper@2.14.1 puppet-syntax@2.6.1 puppet@5.5.6
    Remediation: Upgrade to puppetlabs_spec_helper@2.14.1.

Overview

puppet is an automated configuration management tool.

Affected versions of this package are vulnerable to Denial of Service (DoS) prior to the first pluginsync or may silently ignore Augeas settings.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade puppet to version 6.25.1, 7.12.1 or higher.

References