turbo_boost-commands is a set of commands to help you build robust reactive applications with Rails &…
Historical advisory recorded 24 Oct 2026 23:17:28 UTC. Read the latest advisory.
nvd · CVE-2024-28181
Publishedturbo_boost-commands is a set of commands to help you build robust reactive applications with Rails & Hotwire. 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. 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. This issue has been addressed in versions 0.1.3, and 0.2.2. Users are advised to upgrade. Users unable to upgrade should see the repository GHSA for workaround advice.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2024-28181
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-74
Original publisher date fields
published: 2024-03-14T18:15:07.107
lastModified: 2026-06-17T07:21:09.347
1 source CPE criteria · context only
- cpe:2.3:a:turboboost_commands_project:turboboost_commands:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON