CVE-2025-64097
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 · uneditedNervesHub is a web service that allows users to manage over-the-air (OTA) firmware updates of devices in the field. A vulnerability present starting in version 1.0.0 and prior to version 2.3.0 allowed attackers to brute-force user API tokens due to the predictable format of previously issued tokens. Tokens included user-identifiable components and were not cryptographically secure, making them susceptible to guessing or enumeration. The vulnerability could have allowed unauthorized access to user accounts or API actions protected by these tokens. A fix is available in version 2.3.0 of NervesHub. This version introduces strong, cryptographically-random tokens using `:crypto.strong_rand_bytes/1`, hashing of tokens before database storage to prevent misuse even if the database is compromised, and context-aware token storage to distinguish between session and API tokens. There are no practical workarounds for this issue other than upgrading. In sensitive environments, as a temporary mitigation, firewalling access to the NervesHub server can help limit exposure until an upgrade is possible.
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 · high confidenceNervesHub versions 1.0.0 through 2.2.x issued API tokens with predictable, non-cryptographically secure formats containing user-identifiable components. Attackers could brute-force these tokens to gain unauthorized access to user accounts or perform API actions. The fix in version 2.3.0 implements secure token generation using `:crypto.strong_rand_bytes/1`, hashes tokens before database storage, and separates session from API token storage.
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>= 1.0.0, < 2.3.0CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed NervesHub versionCheck your NervesHub installation's version by inspecting the mix.exs file, a running container label, or the output of `mix nerves_hub.version` if available in your deploymentAffected if The version is 1.0.0 through 2.2.x (any version before 2.3.0)
-
Locate token storage configurationInspect the NervesHub configuration files (config/*.exs) for database connection settings and look for the user_tokens or api_tokens table definitions in the codebaseAffected if API tokens exist in the database and the version is vulnerable
-
Inspect API token formatIf you have database access, query the user_tokens or api_tokens table and examine a sample token value; look for patterns that contain sequential elements, timestamps, or user IDs rather than random bytesAffected if Tokens display predictable patterns or contain user-identifiable substrings (such as user IDs or timestamps embedded in the token string)
-
Check for token hashing implementationSearch the NervesHub source code for token generation functions and verify whether `:crypto.strong_rand_bytes/1` is used and whether tokens are hashed before storage using a secure hash function like bcrypt or pbkdf2Affected if Token generation uses weak randomization or stores tokens in plaintext rather than hashed form
You are affected if your NervesHub version is between 1.0.0 and 2.2.x and you have active API tokens using the predictable, non-hashed format described in the CVE.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.3.0
Upgrade to NervesHub version 2.3.0 or later. As a temporary measure, firewall the NervesHub server to limit exposure until the upgrade can be completed.
2.3.0
- Review the NervesHub 2.3.0 release notes and changelog to understand any changes that may affect your deployment
- Backup the NervesHub database before performing the upgrade
- Upgrade NervesHub to version 2.3.0 using your deployment method (e.g., mix deps.get, mix release)
- After upgrading, inform all users that their existing API tokens have been invalidated and they must generate new tokens
- Have users regenerate their API tokens through the NervesHub web interface or API
- Update any automated systems, scripts, or integrations to use the newly generated tokens
- Verify the upgrade was successful by confirming the web interface is accessible and API authentication works with new tokens
- As an additional temporary mitigation, ensure firewall rules restrict access to the NervesHub server to trusted IPs until the upgrade is complete
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64097 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64097 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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