Skip to content

    Type a page, a command such as keryn scan, or a rule id.

    rails-dependency-versions-v1

    View as Markdown

    4 rules · Keryn Software Licence · rules 0.8.0 · all packs

    How to read a rule
    Severity
    How bad the finding is if it is real: error fails a default gate, warning and info do not.
    Confidence
    P0 exploitable as written; P1 dangerous in context; P2 a heuristic or a posture check: confirm by reading the code.
    False-positive risk
    low: an exact API or flag, so hits are almost always real; medium: the pattern is legitimate in many programs, so check each hit; high: it finds a lead to confirm, so expect benign hits.
    Edge
    The relationship the finding sits on. reaches: content or traffic gets to a thing; calls: one thing invokes another; reads: one thing reads from another; writes: one thing writes to another; sends: data leaves for another party; grants: authority is given or left unchecked; depends_on: something relies on a component it does not verify; trusts: one party believes another without evidence. The boundary it crosses, when there is one: user->prompt (untrusted input reaching a prompt); model->code (model output reaching code, a shell, a query or a page); secret->outside (a secret leaving the trusted side); supply-chain (code, models or prompts pulled in from outside).
    Taxonomy chips
    References for readers who work in OWASP LLM 2025, OWASP Agentic, CWE or NIST AI RMF. They say where a rule belongs, not that a framework is satisfied.

    warning generic ruby, rails, bundler

    The application pins or locks a Rails release line that no longer receives security fixes (7.1 or older). Every Rails advisory published after the line’s end of life stays unfixed here, including SQL injection, XSS and denial-of-service issues in Action Pack, Action View and Active Record. Upgrade to a maintained Rails release.

    Confidence P1: dangerous in context. False-positive risk low: an exact API or flag, so hits are almost always real.

    Edge inspected: depends_on something relies on a component it does not verify.

    CWE-1104 LLM03

    Fix: Move to a Rails release that is still in its security-maintenance window, run the upgrade guide for each minor version in between, and keep Gemfile.lock under dependency review so the next end of life is noticed.

    References: https://rubyonrails.org/maintenance · https://endoflife.date/rails

    keryn.rails.deps.rails-version-eol-manifest

    Section titled “keryn.rails.deps.rails-version-eol-manifest”

    warning generic ruby, rails, bundler

    The application pins or locks a Rails release line that no longer receives security fixes (7.1 or older). Every Rails advisory published after the line’s end of life stays unfixed here, including SQL injection, XSS and denial-of-service issues in Action Pack, Action View and Active Record. Upgrade to a maintained Rails release.

    Confidence P1: dangerous in context. False-positive risk low: an exact API or flag, so hits are almost always real.

    Edge inspected: depends_on something relies on a component it does not verify.

    CWE-1104 LLM03

    Fix: Move to a Rails release that is still in its security-maintenance window, run the upgrade guide for each minor version in between, and keep Gemfile.lock under dependency review so the next end of life is noticed.

    References: https://rubyonrails.org/maintenance · https://endoflife.date/rails

    warning generic ruby, bundler

    The project selects a Ruby version line that no longer receives security fixes (3.0 or older). Interpreter and standard-library vulnerabilities found since then (OpenSSL bindings, URI, REXML, WEBrick, Psych) stay unfixed. Upgrade to a maintained Ruby.

    Confidence P1: dangerous in context. False-positive risk low: an exact API or flag, so hits are almost always real.

    Edge inspected: depends_on something relies on a component it does not verify.

    CWE-1104 LLM03

    Fix: Update .ruby-version and the Gemfile ruby directive to a Ruby release still in normal or security maintenance, and rebuild the lockfile under it.

    References: https://www.ruby-lang.org/en/downloads/branches/ · https://endoflife.date/ruby

    keryn.rails.deps.gem-version-with-advisory

    Section titled “keryn.rails.deps.gem-version-with-advisory”

    warning generic ruby, rails, bundler

    A Rails-stack gem is locked or pinned at a version with a published security advisory: json before 1.7.7 (CVE-2013-0269, unsafe object creation), loofah before 2.19.1 (CVE-2022-23514/23515/23516, XSS and ReDoS), rails-html-sanitizer before 1.6.1 (CVE-2018-3741, CVE-2022-32209, CVE-2024-53985 and others, XSS), sprockets before 2.12.5 / 3.7.2 (CVE-2018-3760, path traversal) or actionpack-page_caching before 1.2.2 (CVE-2020-8159, arbitrary file write). Upgrade the gem.

    Confidence P1: dangerous in context. False-positive risk low: an exact API or flag, so hits are almost always real.

    Edge inspected: depends_on something relies on a component it does not verify.

    CWE-1395 LLM03

    Fix: bundle update the named gem to a fixed release and commit the new Gemfile.lock; keryn scan --online checks every locked gem against the full advisory database.

    References: https://github.com/advisories?query=ecosystem%3Arubygems · https://nvd.nist.gov/vuln/detail/cve-2018-3760 · https://nvd.nist.gov/vuln/detail/cve-2013-0269