dbcve.org
RotpApplication · Rotp Project

CVE-2024-28862

MEDIUM · 5.5 CVSS v3.1 Published 2024-03-16
Fix available
A fix is available. Upgrade to 6.3.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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
The Ruby One Time Password library (ROTP) is an open source library for generating and validating one time passwords. Affected versions had overly permissive default permissions. Users should patch to version 6.3.0. Users unable to patch may correct file permissions after installation.

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

The Ruby One Time Password library (ROTP) versions prior to 6.3.0 shipped with overly permissive default file permissions, potentially exposing sensitive OTP secrets or configuration data to unauthorized users on the same system.

MitigationUpgrade ROTP to version 6.3.0 or later. If patching is not feasible, manually correct file permissions to restrict access after installation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RotpApplication
Affected:>= 6.2.1, < 6.3.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check installed ROTP gem version
    Run `gem list rotp` or `gem info rotp` to see the currently installed version
    Affected if Version is 6.2.1, 6.2.2, or any version >= 6.2.1 and < 6.3.0
  2. Locate ROTP gem installation directory
    Run `gem which rotp` or check gem environment with `gem environment` to find the gem installation path
    Affected if The gem is installed in a shared system location (common on multi-user systems)
  3. Inspect file permissions on gem directory
    Run `ls -la` on the ROTP gem directory (typically /var/lib/gems/*/gems/rotp-* or similar path)
    Affected if Any files or directories show permissions like 0644, 0755, or any permission that grants read or execute access to 'others' (the 'o' column shows '+' or permissions like 'rwxr-xr-x')
  4. Check permissions on configuration or data files
    Look for any YAML, JSON, or config files within the gem directory that may contain secrets: `find /path/to/rotp/gem -type f -name '*.yml' -o -name '*.yaml' -o -name '*.json' | xargs ls -la`
    Affected if These files are readable by users other than the owner (permissions include 'r--r--r--' or 'rw-r--r--')
  5. Verify if running in a multi-user environment
    Check if the system has multiple user accounts using `who` or check /etc/passwd for multiple users
    Affected if Multiple users exist on the system and the gem is installed in a shared location with permissive permissions

A user is affected if the ROTP gem version is 6.2.1 through 6.2.x (below 6.3.0) AND the gem files are installed in a shared location with permissions allowing other users to read sensitive files.

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
Upgrade available Upgrade to 6.3.0 or later
Fixed in 6.3.0
Interim mitigation

Upgrade ROTP to version 6.3.0 or later. If patching is not feasible, manually correct file permissions to restrict access after installation.

Recommended fix High confidence

6.3.0

  1. Update the rotp gem to version 6.3.0 or later by running: gem install rotp -v 6.3.0 (or bundle update rotp if using Bundler)
  2. Verify the installed version matches or exceeds 6.3.0: gem list rotp
  3. Test that OTP generation and validation functionality continues to work correctly after the upgrade
  4. For users unable to upgrade: After installation, manually correct file permissions on the installed gem files to remove overly permissive access (e.g., chmod 644 for files, 755 for directories, removing world-readable/writeable permissions)

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

Fix this in Rotp Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28862 — 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-28862 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