saigkill/hoe-packaging:Gemfile.lock

Vulnerabilities

7 via 9 paths

Dependencies

29

Source

GitHub

Commit

a2a697f5

Find, fix and prevent vulnerabilities in your code.

Severity
  • 5
  • 2
Status
  • 7
  • 0
  • 0

high severity

Arbitrary Code Loading

  • Vulnerable module: puppet
  • Introduced through: hoe-packaging@1.2.6

Detailed paths

  • Introduced through: saigkill/hoe-packaging:Gemfile.lock@saigkill/hoe-packaging#a2a697f57d5371ed6247475c53d1c1f4921fb9ea hoe-packaging@1.2.6 fpm-cookery@0.35.1 puppet@3.6.2
    Remediation: Upgrade to hoe-packaging@1.2.6.

Overview

puppet is an an automated configuration management tool.

Affected versions of this package are vulnerable to Arbitrary Code Loading. With a specially crafted configuration file an attacker could get pxp-agent to load arbitrary code with privilege escalation.

Remediation

Upgrade puppet to versions 5.3.7, 5.5.2 or higher.

References

high severity

Denial of Service (DoS)

  • Vulnerable module: json
  • Introduced through: hoe-packaging@1.2.6

Detailed paths

  • Introduced through: saigkill/hoe-packaging:Gemfile.lock@saigkill/hoe-packaging#a2a697f57d5371ed6247475c53d1c1f4921fb9ea hoe-packaging@1.2.6 fpm@1.11.0 json@1.8.6
  • Introduced through: saigkill/hoe-packaging:Gemfile.lock@saigkill/hoe-packaging#a2a697f57d5371ed6247475c53d1c1f4921fb9ea hoe-packaging@1.2.6 fpm-cookery@0.35.1 json@1.8.6
  • Introduced through: saigkill/hoe-packaging:Gemfile.lock@saigkill/hoe-packaging#a2a697f57d5371ed6247475c53d1c1f4921fb9ea hoe-packaging@1.2.6 fpm-cookery@0.35.1 fpm@1.11.0 json@1.8.6

Overview

json is a JSON implementation as a Ruby extension in C.

Affected versions of this package are vulnerable to Denial of Service (DoS). When parsing certain JSON documents, the json gem (including the one bundled with Ruby) can be coerced into creating arbitrary objects in the target system.

This is the same issue as CVE-2013-0269. The previous fix was incomplete, which addressed JSON.parse(user_input), but didn’t address some other styles of JSON parsing including JSON(user_input) and JSON.parse(user_input, nil).

See CVE-2013-0269 in detail.

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 json to version 2.3.0 or higher.

References

high severity

Deserialization of Untrusted Data

  • Vulnerable module: puppet
  • Introduced through: hoe-packaging@1.2.6

Detailed paths

  • Introduced through: saigkill/hoe-packaging:Gemfile.lock@saigkill/hoe-packaging#a2a697f57d5371ed6247475c53d1c1f4921fb9ea hoe-packaging@1.2.6 fpm-cookery@0.35.1 puppet@3.6.2
    Remediation: Upgrade to hoe-packaging@1.2.6.

Overview

puppet is an automated configuration management tool.

Affected versions of this package are vulnerable to Deserialization of Untrusted Data. It allows deserializing data off the wire (from the agent to the server, in this case) with an attacker-specified format. This could be used to force YAML deserialization in an unsafe manner, which would lead to remote code execution. This change constrains the format of data on the wire to PSON or safely decoded YAML.

Remediation

Upgrade puppet to version 4.10.1 or higher.

References

high severity

Privilege Escalation

  • Vulnerable module: puppet
  • Introduced through: hoe-packaging@1.2.6

Detailed paths

  • Introduced through: saigkill/hoe-packaging:Gemfile.lock@saigkill/hoe-packaging#a2a697f57d5371ed6247475c53d1c1f4921fb9ea hoe-packaging@1.2.6 fpm-cookery@0.35.1 puppet@3.6.2
    Remediation: Upgrade to hoe-packaging@1.2.6.

Overview

puppet is a Server automation framework and application.

Affected versions of this package are vulnerable to DLL preloading attacks which could lead to a privilege escalation.

Remediation

Upgrade puppet to versions 5.3.7, 5.5.2 or higher.

References

high severity

Privilege Escalation

  • Vulnerable module: puppet
  • Introduced through: hoe-packaging@1.2.6

Detailed paths

  • Introduced through: saigkill/hoe-packaging:Gemfile.lock@saigkill/hoe-packaging#a2a697f57d5371ed6247475c53d1c1f4921fb9ea hoe-packaging@1.2.6 fpm-cookery@0.35.1 puppet@3.6.2
    Remediation: Upgrade to hoe-packaging@1.2.6.

Overview

puppet is a Server automation framework and application.

Affected versions of this package are vulnerable to Privilege Escalation. An unprivileged user on Windows agents could write custom facts that can escalate privileges on the next puppet run.

Remediation

Upgrade puppet to versions 5.3.7, 5.5.2 or higher.

References

medium severity

Information Exposure

  • Vulnerable module: puppet
  • Introduced through: hoe-packaging@1.2.6

Detailed paths

  • Introduced through: saigkill/hoe-packaging:Gemfile.lock@saigkill/hoe-packaging#a2a697f57d5371ed6247475c53d1c1f4921fb9ea hoe-packaging@1.2.6 fpm-cookery@0.35.1 puppet@3.6.2
    Remediation: Upgrade to hoe-packaging@1.2.6.

Overview

puppet is an automated administrative engine for your Linux, Unix, and Windows systems, performs administrative tasks based on a centralized specification.

Affected versions of this package are vulnerable to Information Exposure. It was possible for the agent to retrieve facts from an environment that it was not classified to retrieve from.

Remediation

Upgrade puppet to version 5.3.4 or higher.

References

medium severity

Insecure Permissions

  • Vulnerable module: puppet
  • Introduced through: hoe-packaging@1.2.6

Detailed paths

  • Introduced through: saigkill/hoe-packaging:Gemfile.lock@saigkill/hoe-packaging#a2a697f57d5371ed6247475c53d1c1f4921fb9ea hoe-packaging@1.2.6 fpm-cookery@0.35.1 puppet@3.6.2
    Remediation: Upgrade to hoe-packaging@1.2.6.

Overview

puppet is an automated administrative engine for your Linux, Unix, and Windows systems, performs administrative tasks based on a centralized specification.

Affected versions of this package are vulnerable to Insecure Permissions. It was possible to install a module with world writable permissions.

Remediation

Upgrade puppet to version 5.3.4 or higher.

References