cvss_cli 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 586a1192e87c8d2d0048cf5dceecdb4eab527f2fd6ee20ab598d0bd36ba1c910
+  data.tar.gz: d644c2c712c14b49ada11f8a39dbe5483c3bb1d1645804b08aabe4d991e192d8
+SHA512:
+  metadata.gz: 4753ac27b59aa74b91ddace53c3d4e90d6ec2cf2ca5b6c331b9d886daca9105606074481e9cbb6e3efac0c29a95b8f3a00031360a0b538832f7738f367be036a
+  data.tar.gz: db1e33b6dff5225ceb222381ac9282ec57df88566975e11dd7f6e0854e06e0ac755dfc2f31ec8ac3f564c202cd2ada6ffd8045fca50d4561f126c33b47d9f47b

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/Gemfile

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in cvss_cli.gemspec
+gemspec
+
+gem "rake", "~> 13.0"
+
+gem "rspec", "~> 3.0"

data/Gemfile.lock

@@ -0,0 +1,42 @@
+PATH
+  remote: .
+  specs:
+    cvss_cli (0.1.0)
+      clipboard (~> 1.3, >= 1.3.6)
+      colorize (~> 0.8.1)
+      ffi (~> 1.15, >= 1.15.5)
+      thor (~> 1.2, >= 1.2.1)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    clipboard (1.3.6)
+    colorize (0.8.1)
+    diff-lcs (1.5.0)
+    ffi (1.15.5)
+    rake (13.0.6)
+    rspec (3.11.0)
+      rspec-core (~> 3.11.0)
+      rspec-expectations (~> 3.11.0)
+      rspec-mocks (~> 3.11.0)
+    rspec-core (3.11.0)
+      rspec-support (~> 3.11.0)
+    rspec-expectations (3.11.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.11.0)
+    rspec-mocks (3.11.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.11.0)
+    rspec-support (3.11.0)
+    thor (1.2.1)
+
+PLATFORMS
+  x86_64-linux
+
+DEPENDENCIES
+  cvss_cli!
+  rake (~> 13.0)
+  rspec (~> 3.0)
+
+BUNDLED WITH
+   2.3.12

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2022 ferdl
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,42 @@
+# CvssCli
+
+Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/cvss_cli`. To experiment with that code, run `bin/console` for an interactive prompt.
+
+TODO: Delete this and the text above, and describe your gem
+
+## Installation
+
+Install the gem and add to the application's Gemfile by executing:
+
+    $ bundle add cvss_cli
+
+If bundler is not being used to manage dependencies, install the gem by executing:
+
+    $ gem install cvss_cli
+
+CvssCli needs a working directory to persist cvss strings between multiple invocations.
+Set the environment variable CVSS_CLI_PATH, e.g. via
+
+    $ echo "export CVSS_CLI_PATH=\"$HOME/.cvss_cli\"" >> ~/.bashrc
+
+The cvss3_1.yaml containing all the metrics, their descriptions, etc. also needs to be placed there,
+so copy it into this folder. 
+
+## Usage
+
+
+See `cvss help` for more information.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/cvss_cli.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).

data/Rakefile

@@ -0,0 +1,8 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task default: :spec

data/cvss3_1.yaml

@@ -0,0 +1,398 @@
+metric_groups:
+  base:
+    av:
+      name: Attack Vector (AV)
+      desc: This metric reflects the context by which vulnerability exploitation is possible. The Base Score increases the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable component.
+      values:
+        n:
+          name: Network (N)
+          desc: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
+          numerical: 0.85
+        a:
+          name: Adjacent (A)
+          desc: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
+          numerical: 0.62
+        l:
+          name: Local (L)
+          desc: "The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document)."
+          numerical: 0.55
+        p:
+          name: Physical (P)
+          desc: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
+          numerical: 0.2
+    ac:
+      name: Attack Complexity (AC)
+      desc: This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Such conditions may require the collection of more information about the target or computational exceptions. The assessment of this metric excludes any requirements for user interaction in order to exploit the vulnerability. If a specific configuration is required for an attack to succeed, the Base metrics should be scored assuming the vulnerable component is in that configuration.
+      values:
+        l:
+          name: Low (L)
+          desc: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
+          numerical: 0.77
+        h:
+          name: High (H)
+          desc: "A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack)."
+          numerical: 0.44
+    pr:
+      name: Privileges Required (PR)
+      desc: This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.
+      values:
+        n:
+          name: None (N)
+          desc: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
+          numerical: 0.85
+          numerical_changed: 0.85
+        l:
+          name: Low (L)
+          desc: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
+          numerical: 0.62
+          numerical_changed: 0.68
+        h:
+          name: High (H)
+          desc: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
+          numerical: 0.27
+          numerical_changed: 0.5
+    ui:
+      name: User Interaction (UI)
+      desc: This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise the vulnerable component. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.
+      values:
+        n:
+          name: None (N)
+          desc: The vulnerable system can be exploited without any interaction from any user.
+          numerical: 0.85
+        r:
+          name: Required (R)
+          desc: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
+          numerical: 0.62
+    s:
+      name: Scope (S)
+      desc: Does a successful attack impact a component other than the vulnerable component? If so, the Base Score increases and the Confidentiality, Integrity and Authentication metrics should be scored relative to the impacted component.
+      values:
+        u:
+          name: Unchanged (U)
+          desc: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
+        c:
+          name: Changed (C)
+          desc: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
+    c:
+      name: Confidentiality (C)
+      desc: This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
+      values:
+        n:
+          name: None (N)
+          desc: There is no loss of confidentiality within the impacted component.
+          numerical: 0
+        l:
+          name: Low (L)
+          desc: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
+          numerical: 0.22
+        h:
+          name: High (H)
+          desc: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
+          numerical: 0.56
+    i:
+      name: Integrity (I)
+      desc: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.
+      values:
+        n:
+          name: None (N)
+          desc: There is no loss of integrity within the impacted component.
+          numerical: 0
+        l:
+          name: Low (L)
+          desc: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
+          numerical: 0.22
+        h:
+          name: High (H)
+          desc: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
+          numerical: 0.56
+    a:
+      name: Availability (A)
+      desc: This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. It refers to the loss of availability of the impacted component itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of an impacted component.
+      values:
+        n:
+          name: None (N)
+          desc: There is no impact to availability within the impacted component.
+          numerical: 0
+        l:
+          name: Low (L)
+          desc: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.
+          numerical: 0.22
+        h:
+          name: High (H)
+          desc: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
+          numerical: 0.56
+  temporal:
+    e:
+      name: Exploit Code Maturity (E)
+      desc: This metric measures the likelihood of the vulnerability being attacked, and is typically based on the current state of exploit techniques, exploit code availability, or active, 'in-the-wild' exploitation.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: Assigning this value indicates there is insufficient information to choose one of the other values, and has no impact on the overall Temporal Score, i.e., it has the same effect on scoring as assigning High.
+          numerical: 1
+        u:
+          name: Unproven (U)
+          desc: No exploit code is available, or an exploit is theoretical.
+          numerical: 0.91
+        p:
+          name: Proof-of-Concept (P)
+          desc: Proof-of-concept exploit code is available, or an attack demonstration is not practical for most systems. The code or technique is not functional in all situations and may require substantial modification by a skilled attacker.
+          numerical: 0.94
+        f:
+          name: Functional (F)
+          desc: Functional exploit code is available. The code works in most situations where the vulnerability exists.
+          numerical: 0.97
+        h:
+          name: High (H)
+          desc: Functional autonomous code exists, or no exploit is required (manual trigger) and details are widely available. Exploit code works in every situation, or is actively being delivered via an autonomous agent (such as a worm or virus). Network-connected systems are likely to encounter scanning or exploitation attempts. Exploit development has reached the level of reliable, widely-available, easy-to-use automated tools.
+          numerical: 1
+    rl:
+      name: Remediation Level (RL)
+      desc: The Remediation Level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: Assigning this value indicates there is insufficient information to choose one of the other values, and has no impact on the overall Temporal Score, i.e., it has the same effect on scoring as assigning Unavailable.
+          numerical: 1
+        o:
+          name: Official Fix (O)
+          desc: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
+          numerical: 0.95
+        t:
+          name: Temporary Fix (T)
+          desc: There is an official but temporary fix available. This includes instances where the vendor issues a temporary hotfix, tool, or workaround.
+          numerical: 0.96
+        w:
+          name: Workaround (W)
+          desc: There is an unofficial, non-vendor solution available. In some cases, users of the affected technology will create a patch of their own or provide steps to work around or otherwise mitigate the vulnerability.
+          numerical: 0.97
+        u:
+          name: Unavailable (U)
+          desc: There is either no solution available or it is impossible to apply.
+          numerical: 1
+    rc:
+      name: Report Confidence (RC)
+      desc: This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes only the existence of vulnerabilities are publicized, but without specific details. For example, an impact may be recognized as undesirable, but the root cause may not be known. The vulnerability may later be corroborated by research which suggests where the vulnerability may lie, though the research may not be certain. Finally, a vulnerability may be confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: Assigning this value indicates there is insufficient information to choose one of the other values, and has no impact on the overall Temporal Score, i.e., it has the same effect on scoring as assigning Confirmed.
+          numerical: 1
+        u:
+          name: Unknown (U)
+          desc: There are reports of impacts that indicate a vulnerability is present. The reports indicate that the cause of the vulnerability is unknown, or reports may differ on the cause or impacts of the vulnerability. Reporters are uncertain of the true nature of the vulnerability, and there is little confidence in the validity of the reports or whether a static Base score can be applied given the differences described. An example is a bug report which notes that an intermittent but non-reproducible crash occurs, with evidence of memory corruption suggesting that denial of service, or possible more serious impacts, may result.
+          numerical: 0.92
+        r:
+          name: Reasonable (R)
+          desc: Significant details are published, but researchers either do not have full confidence in the root cause, or do not have access to source code to fully confirm all of the interactions that may lead to the result. Reasonable confidence exists, however, that the bug is reproducible and at least one impact is able to be verified (Proof-of-concept exploits may provide this). An example is a detailed write-up of research into a vulnerability with an explanation (possibly obfuscated or 'left as an exercise to the reader') that gives assurances on how to reproduce the results.
+          numerical: 0.96
+        c:
+          name: Confirmed (C)
+          desc: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.
+          numerical: 1
+  environmental:
+    cr:
+      name: Confidentiality Requirement (CR)
+      desc: These metrics enable the analyst to customize the CVSS score depending on the importance of the Confidentiality of the affected IT asset to a user’s organization, relative to other impacts. This metric modifies the environmental score by reweighting the Modified Confidentiality impact metric versus the other modified impacts.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: Assigning this value indicates there is insufficient information to choose one of the other values, and has no impact on the overall Environmental Score, i.e., it has the same effect on scoring as assigning Medium.
+          numerical: 1
+        l:
+          name: Low (L)
+          desc: Loss of Confidentiality is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).
+          numerical: 0.5
+        m:
+          name: Medium (M)
+          desc: Assigning this value to the metric will not influence the score.
+          numerical: 1
+        h:
+          name: High (H)
+          desc: Loss of Confidentiality is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).
+          numerical: 1.5
+    ir:
+      name: Integrity Requirement (IR)
+      desc: These metrics enable the analyst to customize the CVSS score depending on the importance of the Integrity of the affected IT asset to a user’s organization, relative to other impacts. This metric modifies the environmental score by reweighting the Modified Integrity impact metric versus the other modified impacts.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: Assigning this value indicates there is insufficient information to choose one of the other values, and has no impact on the overall Environmental Score, i.e., it has the same effect on scoring as assigning Medium.
+          numerical: 1
+        l:
+          name: Low (L)
+          desc: Loss of Integrity is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).
+          numerical: 0.5
+        m:
+          name: Medium (M)
+          desc: Assigning this value to the metric will not influence the score.
+          numerical: 1
+        h:
+          name: High (H)
+          desc: Loss of Integrity is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).
+          numerical: 1.5
+    ar:
+      name: Availability Requirement (AR)
+      desc: These metrics enable the analyst to customize the CVSS score depending on the importance of the Availability of the affected IT asset to a user’s organization, relative to other impacts. This metric modifies the environmental score by reweighting the Modified Availability impact metric versus the other modified impacts.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: Assigning this value indicates there is insufficient information to choose one of the other values, and has no impact on the overall Environmental Score, i.e., it has the same effect on scoring as assigning Medium.
+          numerical: 1
+        l:
+          name: Low (L)
+          desc: Loss of Availability is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).
+          numerical: 0.5
+        m:
+          name: Medium (M)
+          desc: Assigning this value to the metric will not influence the score.
+          numerical: 1
+        h:
+          name: High (H)
+          desc: Loss of Availability is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).
+          numerical: 1.5
+    mav:
+      name: Modified Attack Vector (MAV)
+      desc: This metric reflects the context by which vulnerability exploitation is possible. The Environmental Score increases the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable component.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: The value assigned to the corresponding Base metric is used.
+        n:
+          name: Network (N)
+          desc: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away.
+          numerical: 0.85
+        a:
+          name: Adjacent Network (A)
+          desc: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN).
+          numerical: 0.62
+        l:
+          name: Local (L)
+          desc: "The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document)."
+          numerical: 0.55
+        p:
+          name: Physical (P)
+          desc: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
+          numerical: 0.2
+    mac:
+      name: Modified Attack Complexity (MAC)
+      desc: This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Such conditions may require the collection of more information about the target or computational exceptions. The assessment of this metric excludes any requirements for user interaction in order to exploit the vulnerability. If a specific configuration is required for an attack to succeed, the Base metrics should be scored assuming the vulnerable component is in that configuration.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: The value assigned to the corresponding Base metric is used.
+        l:
+          name: Low (L)
+          desc: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
+          numerical: 0.77
+        h:
+          name: High (H)
+          desc: "A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack)."
+          numerical: 0.44
+    mpr:
+      name: Modified Privileges Required (MPR)
+      desc: This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: The value assigned to the corresponding Base metric is used.
+        n:
+          name: None (N)
+          desc: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
+          numerical: 0.85
+          numerical_changed: 0.85
+        l:
+          name: Low (L)
+          desc: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
+          numerical: 0.62
+          numerical_changed: 0.68
+        h:
+          name: High (H)
+          desc: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
+          numerical: 0.27
+          numerical_changed: 0.5
+    mui:
+      name: Modified User Interaction (MUI)
+      desc: This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise the vulnerable component. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: The value assigned to the corresponding Base metric is used.
+        n:
+          name: None (N)
+          desc: The vulnerable system can be exploited without any interaction from any user.
+          numerical: 0.85
+        r:
+          name: Required (R)
+          desc: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
+          numerical: 0.62
+    ms:
+      name: Modified Scope (MS)
+      desc: Does a successful attack impact a component other than the vulnerable component? If so, the Base Score increases and the Confidentiality, Integrity and Authentication metrics should be scored relative to the impacted component.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: The value assigned to the corresponding Base metric is used.
+        u:
+          name: Unchanged (U)
+          desc: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
+        c:
+          name: Changed (C)
+          desc: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
+    mc:
+      name: Modified Confidentiality (MC)
+      desc: This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: The value assigned to the corresponding Base metric is used.
+        n:
+          name: None (N)
+          desc: There is no loss of confidentiality within the impacted component.
+          numerical: 0
+        l:
+          name: Low (L)
+          desc: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
+          numerical: 0.22
+        h:
+          name: High (H)
+          desc: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
+          numerical: 0.56
+    mi:
+      name: Modified Integrity (MI)
+      desc: This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: The value assigned to the corresponding Base metric is used.
+        n:
+          name: None (N)
+          desc: There is no loss of integrity within the impacted component.
+          numerical: 0
+        l:
+          name: Low (L)
+          desc: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
+          numerical: 0.22
+        h:
+          name: High (H)
+          desc: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
+          numerical: 0.56
+    ma:
+      name: Modified Availability (MA)
+      desc: This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. It refers to the loss of availability of the impacted component itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of an impacted component.
+      values:
+        x:
+          name: Not Defined (X)
+          desc: The value assigned to the corresponding Base metric is used.
+        n:
+          name: None (N)
+          desc: There is no impact to availability within the impacted component.
+          numerical: 0
+        l:
+          name: Low (L)
+          desc: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.
+          numerical: 0.22
+        h:
+          name: High (H)
+          desc: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
+          numerical: 0.56

data/cvss_cli.gemspec

@@ -0,0 +1,42 @@
+# frozen_string_literal: true
+
+require_relative "lib/cvss_cli/version"
+
+Gem::Specification.new do |spec|
+  spec.name = "cvss_cli"
+  spec.version = CvssCli::VERSION
+  spec.authors = ["Martin Haunschmid, Daniel Haider"]
+  spec.email = ["contact@martinhaunschmid.com"]
+
+  spec.summary = "CLI Tool to calculate CVSS Scores"
+  spec.description = "A simple CLI Tool to calculate CVSS Scores"
+  spec.homepage = "https://github.com/martinhaunschmid/cvss.cli"
+  spec.license = "MIT"
+  spec.required_ruby_version = ">= 2.6.0"
+
+  spec.metadata["homepage_uri"] = spec.homepage
+  spec.metadata["source_code_uri"] = "https://github.com/martinhaunschmid/cvss.cli"
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files = Dir.chdir(__dir__) do
+    `git ls-files -z`.split("\x0").reject do |f|
+      (f == __FILE__) || f.match(%r{\A(?:(?:bin|test|spec|features)/|\.(?:git|travis|circleci)|appveyor)})
+    end
+  end
+  spec.bindir = "exe"
+  spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  # Uncomment to register a new dependency of your gem
+  # spec.add_dependency "example-gem", "~> 1.0"
+  spec.add_development_dependency "rspec", "~> 3.4"
+
+  spec.add_runtime_dependency 'thor', '~> 1.2', '>= 1.2.1'
+  spec.add_runtime_dependency 'colorize', '~> 0.8.1'
+  spec.add_runtime_dependency "clipboard", '~> 1.3', '>= 1.3.6'
+  spec.add_runtime_dependency "ffi", '~> 1.15', '>= 1.15.5'
+
+  # For more information and examples about making a new gem, check out our
+  # guide at: https://bundler.io/guides/creating_gem.html
+end

data/exe/cvss

@@ -0,0 +1,15 @@
+#!/usr/bin/env ruby
+require "cvss_cli"
+require 'colorize'
+
+if ENV['CVSS_CLI_PATH'].nil?
+  puts 'CVSS_CLI_PATH not set. Please set this environment variable in order to use cvss_cli.'.red
+  exit 1
+end
+
+unless File.exist?(File.join(ENV['CVSS_CLI_PATH'], "cvss3_1.yaml"))
+  puts "cvss3_1.yaml not found. Please copy it to #{File.join(ENV['CVSS_CLI_PATH'])}".red
+  exit 1
+end
+
+CvssCli::CLI.start

data/lib/cvss_cli/cvss.rb

@@ -0,0 +1,264 @@
+require 'cvss_cli/metric_group'
+
+module CvssCli
+  class Cvss
+
+    attr_reader :groups, :metrics
+
+    def initialize(cvss_string = nil)
+      @groups = Hash.new
+      @metrics = Hash.new
+
+      file = YAML.load_file(File.join(ENV['CVSS_CLI_PATH'], "cvss3_1.yaml"))
+      file['metric_groups'].each do |name, metric_group|
+        group = MetricGroup.new(name, metric_group)
+        @groups[name] = group
+        @metrics.merge!(group.metrics)
+      end
+
+      parse_cvss_string(cvss_string) unless cvss_string.nil?
+    end
+
+    def set_metric(metric, value)
+      if value != 'NIL'
+        @metrics[metric.downcase].set_value(value)
+      end
+    end
+
+    def clear
+      @metrics.values.each do |metric|
+        metric.clear_value
+      end
+    end
+
+    def print_status(full = false)
+      @groups.values.each do |group|
+        print_group(group, full)
+      end
+      print_score
+      print_cvss
+    end
+
+    def get_score
+      score = calculate_base_score
+      if @groups['temporal'].any_metric_set?
+        score = calculate_temporal_score(score)
+      end
+      if @groups['environmental'].any_metric_set?
+        score = calculate_environmental_score
+      end
+      score
+    end
+
+    def get_rating(score)
+      if score != roundup(score)
+        raise RuntimeError.new "Called with invalid value. Please round up your score to the smallest number, specified to 1 decimal place, that is equal to or higher than its input"
+      end
+
+      if score < 0 or score > 10
+        raise RuntimeError.new "Score must be betweeen 0 and 10."
+      end
+
+      if score == 0.0
+        'None'
+      elsif score >= 0.1 and score <= 3.9
+        'Low'
+      elsif score >= 4.0 and score <= 6.9
+        'Medium'
+      elsif score >= 7.0 and score <= 8.9
+        'High'
+      elsif score >= 9.0 and score <= 10
+        'Critical'
+      end
+    end
+
+    def to_s
+      s = ""
+      @groups.values.each do |group|
+        s += group.get_cvss_string
+      end
+      "CVSS:3.1/" + s.delete_suffix('/')
+    end
+
+    def parse_cvss_string(cvss_string)
+      s = cvss_string.delete_prefix('CVSS:3.1/')
+      s.split('/').each do |pair|
+        metric = pair.split(':')[0]
+        value = pair.split(':')[1]
+        set_metric(metric, value)
+      end
+    end
+
+    private
+
+    def print_score
+      score = get_score
+
+      unless score.nil?
+        rating = get_rating(score)
+        score_string = "#{score} (#{rating})"
+
+        case rating
+        when "Low"
+          score_string = score_string.light_yellow
+        when "Medium"
+          score_string = score_string.yellow
+        when "High"
+          score_string = score_string.light_red
+        when "Critical"
+          score_string = score_string.red.underline
+        end
+        puts score_string
+      end
+    end
+
+    def print_cvss
+      cvss_string = self.to_s.gsub("NIL", "NIL".light_black.italic)
+      puts cvss_string
+    end
+
+    def print_group(group, full)
+      if group.any_metric_set?
+        puts group.name.capitalize.underline
+
+        if full
+          group.metrics.values.each do |metric|
+            left_side = metric.name.ljust(group.print_size)
+
+            vals = []
+            metric.values.values.each do |v|
+              if v.name == metric.get_value&.name
+                vals << v.name.white
+              else
+                vals << v.name.light_black
+              end
+            end
+
+            right_side = vals.join(', ')
+            puts "#{left_side} | #{right_side}"
+          end
+        else
+          group.metrics.values.each do |metric|
+            puts "#{metric.name.ljust(group.print_size)} | #{metric.get_value&.name}"
+          end
+        end
+
+        puts ""
+      end
+    end
+
+    def calculate_base_score
+      unless groups['base'].all_metrics_set?
+        return nil
+      end
+
+      c = get_numerical_value 'c'
+      i = get_numerical_value 'i'
+      a = get_numerical_value 'a'
+      av = get_numerical_value 'av'
+      ac = get_numerical_value 'ac'
+      ui = get_numerical_value 'ui'
+      scope_changed = (get_value 's') == 'c'
+
+      pr = scope_changed ? (get_numerical_changed_value 'pr') : (get_numerical_value 'pr')
+      iss = 1 - ((1 - c) * (1 - i) * (1 - a))
+
+      impact = scope_changed ? (7.52 * (iss - 0.029) - 3.25 * (iss - 0.02) ** 15) : (6.42 * iss)
+      exploitability = 8.22 * av * ac * pr * ui
+
+      if impact <= 0
+        0
+      elsif scope_changed
+        roundup([1.08 * (impact + exploitability), 10].min)
+      else
+        roundup([(impact + exploitability), 10].min)
+      end
+
+    end
+
+    def calculate_temporal_score(base_score)
+      if groups['temporal'].any_metric_set?
+        e = get_numerical_value 'e'
+        rl = get_numerical_value 'rl'
+        rc = get_numerical_value 'rc'
+        roundup(base_score * e * rl * rc)
+      else
+        base_score
+      end
+    end
+
+    def calculate_environmental_score
+      mc = get_modified_numerical_value('mc', 'c')
+      mi = get_modified_numerical_value('mi', 'i')
+      ma = get_modified_numerical_value('ma', 'a')
+      mav = get_modified_numerical_value('mav', 'av')
+      mac = get_modified_numerical_value('mac', 'ac')
+      mui = get_modified_numerical_value('mui', 'ui')
+
+      e = get_numerical_value 'e'
+      rl = get_numerical_value 'rl'
+      rc = get_numerical_value 'rc'
+
+      cr = get_numerical_value('cr')
+      ir = get_numerical_value('ir')
+      ar = get_numerical_value('ar')
+
+      ms = (get_value 'ms')
+
+      if !ms.nil? and ms != 'x'
+        scope_changed = (get_value 'ms') == 'c'
+      else
+        scope_changed = (get_value 's') == 'c'
+      end
+
+      mpr = scope_changed ? (get_modified_numerical_changed_value 'mpr', 'pr') : (get_modified_numerical_value 'mpr', 'pr')
+
+      miss = [1 - ((1 - cr * mc) * (1 - ir * mi) * (1 - ar * ma)), 0.915].min
+
+      impact = scope_changed ? (7.52 * (miss - 0.029) - 3.25 * (miss * 0.9731 - 0.02) ** 13) : (6.42 * miss)
+      exploitability = 8.22 * mav * mac * mpr * mui
+
+      if impact <= 0
+        0
+      elsif scope_changed
+        roundup(roundup([1.08 * (impact + exploitability), 10].min) * e * rl * rc)
+      else
+        roundup(roundup([(impact + exploitability), 10].min) * e * rl * rc)
+      end
+    end
+
+    def get_value(metric_key)
+      @metrics[metric_key].get_value&.key
+    end
+
+    def get_numerical_value(metric_key)
+      @metrics[metric_key].get_numerical_value
+    end
+
+    def get_numerical_changed_value(metric_key)
+      @metrics[metric_key].get_numerical_changed_value
+    end
+
+    def get_modified_numerical_value(modified_metric_key, metric_key)
+      if @metrics[modified_metric_key].get_value&.key != 'x'
+        @metrics[modified_metric_key].get_numerical_value
+      else
+        @metrics[metric_key].get_numerical_value
+      end
+    end
+
+    def get_modified_numerical_changed_value(modified_metric_key, metric_key)
+      if @metrics[modified_metric_key].get_value&.key != 'x'
+        @metrics[modified_metric_key].get_numerical_changed_value
+      else
+        @metrics[metric_key].get_numerical_changed_value
+      end
+    end
+
+    def roundup(v)
+      v.ceil(1)
+    end
+
+  end
+
+end

data/lib/cvss_cli/metric.rb

@@ -0,0 +1,53 @@
+require 'cvss_cli/value'
+
+module CvssCli
+  class Metric
+
+    attr_reader :key, :name, :desc, :values, :value
+
+    def initialize(key, name, desc, values)
+      @key = key
+      @name = name
+      @desc = desc
+      @value = nil # todo or add default value?
+      @values = Hash.new
+      values.each do |key, value|
+        @values[key] = Value.new(key, value['name'], value['desc'], value['numerical'], value['numerical_changed'])
+        @value = key if key == 'x' # set default value to Not Defined (X) if the metric has such a value
+      end
+    end
+
+    def set_value(value)
+      if @values.keys.include? value.downcase
+        #puts "Setting #{@name}: #{value.upcase}"
+        @value = value.downcase
+      else
+        puts "Value #{value.upcase} not valid for metric #{@name}. Valid values are: #{(@values.values.collect { |v| v.key.upcase }).join(', ')}".red
+      end
+    end
+
+    def get_value
+      return nil if @value.nil?
+      @values[@value]
+    end
+
+    def get_numerical_value
+      return nil if @value.nil?
+      @values[@value].numerical
+    end
+
+    def get_numerical_changed_value
+      return nil if @value.nil?
+      @values[@value].numerical_changed
+    end
+
+    def clear_value
+      if @values.values.map { |v| v.key }.include? 'x'
+        @value = 'x'
+      else
+        @value = nil
+      end
+    end
+
+  end
+end

data/lib/cvss_cli/metric_group.rb

@@ -0,0 +1,67 @@
+require 'cvss_cli/metric'
+
+module CvssCli
+  class MetricGroup
+
+    attr_reader :name
+    attr_reader :metrics
+
+    def initialize(name, metrics)
+      @name = name
+      @metrics = Hash.new
+
+      metrics.each do |key, metric|
+        @metrics[key] = Metric.new(key, metric['name'], metric['desc'], metric['values'])
+      end
+    end
+
+    def calculate_score(base_score = nil)
+      case @name
+      when "base"
+        calculate_base_score
+      when "temporal"
+        calculate_temporal_score(base_score)
+      when "environmental"
+        calculate_environmental_score
+      else
+        raise NotImplementedError "invalid group name #{@name}"
+      end
+    end
+
+    def get_cvss_string
+      string = ""
+      @metrics.values.each do |metric|
+        if metric.value.nil? or metric.value == 'x'
+          if print_nil_values
+            string += "#{metric.key}:".upcase + "NIL"
+            string += "/"
+          end
+        else
+          string += "#{metric.key}:#{metric.value}".upcase
+          string += "/"
+        end
+      end
+      string
+    end
+
+    def print_size
+      @metrics.values.map { |m| m.name.size }.max
+    end
+
+    def any_metric_set?
+      @metrics.values.any? { |m| !m.value.nil? and m.value != 'x' and m.value != 'NIL' }
+    end
+
+    def all_metrics_set?
+      !@metrics.values.any? { |m| m.value.nil? }
+    end
+
+    private
+
+    def print_nil_values
+      # metrics whose values are nil are only printed in the base group
+      @name == "base"
+    end
+
+  end
+end

data/lib/cvss_cli/value.rb

@@ -0,0 +1,15 @@
+module CvssCli
+  class Value
+
+    attr_reader :key, :name, :desc, :numerical, :numerical_changed
+
+    def initialize(key, name, desc, numerical, numerical_changed)
+      @key = key
+      @name = name
+      @desc = desc
+      @numerical = numerical
+      @numerical_changed = numerical_changed
+    end
+
+  end
+end

data/lib/cvss_cli/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module CvssCli
+  VERSION = "0.1.0"
+end

data/lib/cvss_cli.rb

@@ -0,0 +1,104 @@
+# frozen_string_literal: true
+
+require "cvss_cli/version"
+require "cvss_cli"
+require 'cvss_cli/cvss'
+require "thor"
+require 'yaml'
+require 'colorize'
+require 'net/http'
+require 'json'
+require 'clipboard'
+
+module CvssCli
+  class CLI < Thor
+
+    file_name = File.join(ENV['CVSS_CLI_PATH'], 'cvss_string')
+    cvss_string = File.exist?(file_name) ? File.open(File.join(ENV['CVSS_CLI_PATH'], 'cvss_string')).read : nil
+    @@cvss = Cvss.new(cvss_string)
+
+    @@cvss.metrics.values.each do |metric|
+      desc "#{metric.key} [score]", "#{metric.name}"
+      define_method :"#{metric.key}" do |v = nil|
+        if v.nil?
+          puts metric.desc
+          puts ""
+
+          metric.values.values.each do |value|
+            puts "#{value.name}:"
+            puts "#{value.desc}"
+            puts ""
+          end
+        else
+          metric.set_value(v)
+          write_file
+          invoke :status, []
+          invoke :copy, []
+        end
+      end
+    end
+
+    desc "copy", "Copy current CVSS string to clipboard"
+    def copy()
+      Clipboard.copy @@cvss
+    end
+
+    desc "load cvss_string", "Load the given CVSS string"
+    def load(cvss_string)
+      @@cvss.clear
+      @@cvss.parse_cvss_string(cvss_string)
+      write_file
+      invoke :status, [], full: true
+      invoke :copy, [], []
+    end
+
+    desc "clear", "Clears the current CVSS string"
+    def clear()
+      @@cvss.clear
+      write_file
+      invoke :status, []
+    end
+
+    desc "status", "Show a visual representation of the current CVSS string"
+    method_option :full, aliases: '-f', desc: 'Show all values of metrics, not only the currently selected one.'
+    def status()
+      @@cvss.print_status(options[:full])
+      invoke :copy, [], []
+    end
+
+    desc "cve cve_string", "Loads the CVSS score of the given CVE string"
+    def cve(cve_string)
+      cvss_string = get_cvss_string_from_cve(cve_string)
+      invoke :load, [cvss_string] if cvss_string
+    end
+
+    no_commands do
+      def write_file
+        open(File.join(ENV['CVSS_CLI_PATH'], 'cvss_string'), 'w') do |f|
+          f << @@cvss
+        end
+      end
+
+      def get_cvss_string_from_cve(cve)
+        uri = URI("https://services.nvd.nist.gov/rest/json/cve/1.0/#{cve}")
+        response = Net::HTTP.get(uri)
+        result = JSON.parse(response)
+        if result['result']
+          result['result']['CVE_Items'].each do |cve_item|
+            if cve_item['impact'] && cve_item['impact']['baseMetricV3'] && cve_item['impact']['baseMetricV3']['cvssV3']
+              cvssv3 = cve_item['impact']['baseMetricV3']['cvssV3']
+              if cvssv3['version'].strip == "3.1"
+                return cvssv3['vectorString']
+              end
+            end
+          end
+        else
+          puts "Unable to find CVE.".red
+          return
+        end
+        puts "Could not find CVSS3.1 score for given CVE.".red
+      end
+    end
+
+  end
+end

data/sig/cvss_cli.rbs

@@ -0,0 +1,4 @@
+module CvssCli
+  VERSION: String
+  # See the writing guide of rbs: https://github.com/ruby/rbs#guides
+end

metadata

@@ -0,0 +1,150 @@
+--- !ruby/object:Gem::Specification
+name: cvss_cli
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Martin Haunschmid, Daniel Haider
+autorequire:
+bindir: exe
+cert_chain: []
+date: 2022-07-04 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.4'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.4'
+- !ruby/object:Gem::Dependency
+  name: thor
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.2'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.2.1
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.2'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.2.1
+- !ruby/object:Gem::Dependency
+  name: colorize
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.8.1
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.8.1
+- !ruby/object:Gem::Dependency
+  name: clipboard
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.3'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.3.6
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.3'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.3.6
+- !ruby/object:Gem::Dependency
+  name: ffi
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.15'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.15.5
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.15'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.15.5
+description: A simple CLI Tool to calculate CVSS Scores
+email:
+- contact@martinhaunschmid.com
+executables:
+- cvss
+extensions: []
+extra_rdoc_files: []
+files:
+- ".rspec"
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- cvss3_1.yaml
+- cvss_cli.gemspec
+- exe/cvss
+- lib/cvss_cli.rb
+- lib/cvss_cli/cvss.rb
+- lib/cvss_cli/metric.rb
+- lib/cvss_cli/metric_group.rb
+- lib/cvss_cli/value.rb
+- lib/cvss_cli/version.rb
+- sig/cvss_cli.rbs
+homepage: https://github.com/martinhaunschmid/cvss.cli
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/martinhaunschmid/cvss.cli
+  source_code_uri: https://github.com/martinhaunschmid/cvss.cli
+post_install_message:
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.6.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.3.12
+signing_key:
+specification_version: 4
+summary: CLI Tool to calculate CVSS Scores
+test_files: []