NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · RubyGems

CVE-2024-28181: TurboBoost Commands vulnerable to arbitrary method invocation

highCVSS 3.1 8.1GHSA-mp76-7w5v-pr75

Impact TurboBoost Commands has existing protections in place to guarantee that only public methods on Command classes can be invoked; however, the existing checks aren't as robust as they should be. It's possible for a sophisticated attacker to invoke more methods than should be permitted depending on the the strictness of authorization checks that individual applications enforce.

Published Mar 15, 2024 · Updated Mar 18, 2024

Affected packages

turbo_boost-commands

Ecosystem
RubyGems
Affected
< 0.1.3
Fixed in
0.1.3
Check
bundle info turbo_boost-commands

turbo_boost-commands

Ecosystem
RubyGems
Affected
>= 0.2.0, < 0.2.2
Fixed in
0.2.2
Check
bundle info turbo_boost-commands

@turbo-boost/commands

Ecosystem
npm
Affected
< 0.1.3
Fixed in
0.1.3
Check
npm ls @turbo-boost/commands

@turbo-boost/commands

Ecosystem
npm
Affected
>= 0.2.0, < 0.2.2
Fixed in
0.2.2
Check
npm ls @turbo-boost/commands

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

TurboBoost Commands has existing protections in place to guarantee that only public methods on Command classes can be invoked; however, the existing checks aren't as robust as they should be. It's possible for a sophisticated attacker to invoke more methods than should be permitted depending on the the strictness of authorization checks that individual applications enforce. Being able to call some of these methods can have security implications.

Details

Commands verify that the class must be a Command and that the method requested is defined as a public method; however, this isn't robust enough to guard against all unwanted code execution. The library should more strictly enforce which methods are considered safe before allowing them to be executed.

Patches

Patched in the following versions.

Workarounds

You can add this guard to mitigate the issue if running an unpatched version of the library.

class ApplicationCommand < TurboBoost::Commands::Command
  before_command do
    method_name = params[:name].include?("#") ? params[:name].split("#").last : :perform
    ancestors = self.class.ancestors[0..self.class.ancestors.index(TurboBoost::Commands::Command) - 1]
    allowed = ancestors.any? { |a| a.public_instance_methods(false).any? method_name.to_sym }
    throw :abort unless allowed # ← blocks invocation
    # raise "Invalid Command" unless allowed # ← blocks invocation
  end
end

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology