dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-32978

MEDIUM · 6.6 CVSS v3.1 Published 2024-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Kaminari is a paginator for web app frameworks and object relational mappings. A security vulnerability involving insecure file permissions has been identified in the Kaminari pagination library for Ruby on Rails, concerning insecure file permissions. This vulnerability is of moderate severity due to the potential for unauthorized write access to particular Ruby files managed by the library. Such access could lead to the alteration of application behavior or data integrity issues. Users of affected versions are advised to update to Kaminari version 0.16.2 or later, where file permissions have been adjusted to enhance security. If upgrading is not feasible immediately, review and adjust the file permissions for particular Ruby files in Kaminari to ensure they are only accessible by authorized user.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Insecure file permissions on Ruby files within the Kaminari pagination library for Ruby on Rails allow unauthorized write access. An attacker with filesystem access could modify these Ruby files, potentially altering application behavior or compromising data integrity.

MitigationUpgrade to Kaminari version 0.16.2 or later which contains corrected file permissions. If immediate upgrade is not possible, manually review and restrict file permissions on affected Ruby files to be accessible only by the authorized application user.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Kaminari gem is present
    Run `grep -r 'kaminari' Gemfile Gemfile.lock` or execute `gem list kaminari` to list the installed Kaminari gem
    Affected if Kaminari gem is not found in the project dependencies
  2. Determine installed Kaminari version
    Check the version in Gemfile.lock under the kaminari entry, or run `gem list kaminari -d` to see version details
    Affected if The installed version is lower than 0.16.2 (the fixed version)
  3. Locate Kaminari gem installation path
    Run `gem which kaminari` or `bundle show kaminari` to find the directory where Kaminari Ruby files are installed
    Affected if Kaminari gem files are present on the system
  4. Inspect file permissions on Kaminari Ruby files
    Run `ls -la` on the Kaminari gem directory (e.g., $(gem which kaminari) or the path from step 3) and examine the permission bits on .rb files; check for world-writable (o+w) or group-writable (g+w) flags
    Affected if Any .rb file within the Kaminari gem directory shows write permission for others (o+w) or group (g+w), indicating unauthorized users can modify the files

You are affected if Kaminari version is present and is lower than 0.16.2, or if Kaminari Ruby files have overly permissive write access for non-owner users or groups.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Kaminari version 0.16.2 or later which contains corrected file permissions. If immediate upgrade is not possible, manually review and restrict file permissions on affected Ruby files to be accessible only by the authorized application user.

Recommended fix High confidence

Kaminari version 0.16.2 or later

  1. Check the current Kaminari version in use by running `gem list kaminari` or inspecting your Gemfile
  2. Update Kaminari by running `bundle update kaminari` or by specifying `gem 'kaminari', '~> 0.16.2'` in your Gemfile and running `bundle install`
  3. Verify the upgrade was successful by running `gem list kaminari` and confirming version 0.16.2 or later is installed
  4. If using Rails, restart the application to ensure the new gem version is loaded

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32978 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-32978 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data