CVE-2024-28181

TurboBoost Commands vulnerable to arbitrary method invocation

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

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.

CVE-2024-28181 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.1.3, 0.2.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Patched in the following versions.

• 0.1.3
  • NPM Package
  • Ruby GEM
• 0.2.2
  • NPM Package
  • Ruby GEM

1. What is CVE-2024-28181? CVE-2024-28181 is a high-severity security vulnerability in turbo_boost-commands (rubygems), affecting versions < 0.1.3. It is fixed in 0.1.3, 0.2.2.
2. How severe is CVE-2024-28181? CVE-2024-28181 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2024-28181?
   • turbo_boost-commands (rubygems) (versions < 0.1.3)
   • @turbo-boost/commands (npm) (versions < 0.1.3)
4. Is there a fix for CVE-2024-28181? Yes. CVE-2024-28181 is fixed in 0.1.3, 0.2.2. Upgrade to this version or later.
5. Is CVE-2024-28181 exploitable, and should I be worried? Whether CVE-2024-28181 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-28181 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-28181?
   • Upgrade turbo_boost-commands to 0.1.3 or later
   • Upgrade turbo_boost-commands to 0.2.2 or later
   • Upgrade @turbo-boost/commands to 0.1.3 or later
   • Upgrade @turbo-boost/commands to 0.2.2 or later