Skip to content

karo Metacharacter Handling Remote Command Execution

Critical severity GitHub Reviewed Published May 14, 2022 to the GitHub Advisory Database • Updated Mar 29, 2023

Package

bundler karo (RubyGems)

Affected versions

<= 2.5.2

Patched versions

None

Description

The karo gem through 2.5.2 for Ruby allows Remote command injection via the host field.

A flaw in db.rb is triggered when handling metacharacters. This may allow a remote attacker to execute arbitrary commands.

In particular lines 76 and 95 (as of 2014-06-01) pass unsanitized user supplied input to the command line.

73-      host = "{@configuration["user"]}@{@configuration["host"]}"
74-      cmd  = "ssh #{host} cat {server_db_config_file}"
75-
76:      server_db_config_output = `{cmd}`
79-
--
89- def drop_and_create_local_database(local_db_config)
90-      command = case local_db_config["adapter"]
91-      when "mysql2"
93-      when "postgresql"
95-          dropdb -h #{local_db_config["host"]} -U #{local_db_config["username"]} --if-exists #{local_db_config["database"]}

If this gem is used in the context of a rails application malicious input could lead to remote command injection. As of version 2.5.2 the affected code lines have not changed.

References

Published by the National Vulnerability Database Oct 5, 2018
Published to the GitHub Advisory Database May 14, 2022
Reviewed Mar 29, 2023
Last updated Mar 29, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.764%
(82nd percentile)

Weaknesses

CVE ID

CVE-2014-10075

GHSA ID

GHSA-qfwq-chf4-jvwg

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.