CVE-2024-8796: Under the default configuration, Devise-Two-Factor versions >= 2.2.0 & < 6.0.0 generate TOTP shared secrets th

Q: How urgent is CVE-2024-8796?

Priority 31/100. No elevated risk signals yet.

Routine

MEDIUM 5.3UPGRADE

CVE-2024-8796 is a medium-severity flaw (CVSS 5.3) affecting devise-two-factor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Under the default configuration, Devise-Two-Factor versions >= 2.2.0 & < 6.0.0 generate TOTP shared secrets that are 120 bits instead of the 128-bit minimum defined by RFC 4226. Using a shared secret shorter than the minimum to generate a multi-factor authentication code could make it easier for an attacker to guess the shared secret and generate valid TOTP codes.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 49%)
CISA exploited list	No
Weakness	CWE-331
Published	2024-09-17
Last modified	2026-06-17

Publisher (CNA): Synopsys · Vendor: tinfoilsecurity

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-09-17 18:15 UTCPublished CVE record published
2026-06-17 08:23 UTCUpdated Record last modified

tinfoilsecurity devise-two-factor UPGRADE

Affected: >= 4.0.0 and < 6.0.0 · 1.0.0

Fixed in: 6.0.0

Safe to downgrade to: a release before 1.0.0

1. Check installed version

apt-cache policy devise-two-factor || rpm -q devise-two-factor || devise-two-factor --version

2. UPGRADE to 6.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade devise-two-factor

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade devise-two-factor

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)

apt-cache madison devise-two-factor sudo apt install devise-two-factor=<VERSION_BEFORE_1.0.0> sudo apt-mark hold devise-two-factor

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list devise-two-factor sudo dnf downgrade devise-two-factor-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add devise-two-factor

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-8796?

devise-two-factor: upgrade to 6.0.0. Exact commands for each OS are on this page.

Is CVE-2024-8796 being exploited?

CVE-2024-8796 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-8796 affect?

CVE-2024-8796 affects devise-two-factor. Severity is medium (CVSS 5.3). Under the default configuration, Devise-Two-Factor versions >= 2.2.0 & < 6.0.0 generate TOTP shared secrets that are 120 bits instead of the 128-bit minimum defined by RFC 4226. Using a shared secret shorter than the minimum to generate a m

How urgent is CVE-2024-8796?

Priority 31/100. No elevated risk signals yet.

References

← Back to latest CVEs