CVE-2021-39289
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 · uneditedCertain NetModule devices have Insecure Password Handling (cleartext or reversible encryption), These models with firmware before 4.3.0.113, 4.4.0.111, and 4.5.0.105 are affected: NB800, NB1600, NB1601, NB1800, NB1810, NB2700, NB2710, NB2800, NB2810, NB3700, NB3701, NB3710, NB3711, NB3720, and NB3800.
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 analysisCredentials are stored or transmitted without adequate protection, so an attacker who reaches them can reuse them directly. One weak link here can unravel an entire system. Remediation means strong hashing for stored secrets, encryption in transit, and never writing credentials to logs.
General guidance for the insufficiently protected credentials class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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< 4.3.0.113>= 4.4.0.0, < 4.4.0.111>= 4.5.0.0, < 4.5.0.105CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 · scoped4.3.0.1134.4.0.1114.5.0.105
Upgrade to firmware 4.3.0.113 (for pre-4.3 installs), 4.4.0.111 (for 4.4.x branch), or 4.5.0.105 (for 4.5.x branch) - choose the appropriate version based on your current branch
- 1. Identify the current firmware version installed on the NetModule device by accessing the web interface or using the CLI
- 2. Determine which version branch the current firmware belongs to (pre-4.3, 4.4.x, or 4.5.x)
- 3. Download the appropriate fixed firmware version from NetModule's official support portal or from www.netmodule.com
- 4. For firmware versions < 4.3.0.113, upgrade to version 4.3.0.113 or later
- 5. For firmware versions >= 4.4.0.0 and < 4.4.0.111, upgrade to version 4.4.0.111 or later
- 6. For firmware versions >= 4.5.0.0 and < 4.5.0.105, upgrade to version 4.5.0.105 or later
- 7. Upload the firmware file through the device's web interface or via CLI using the firmware update function
- 8. After upgrade, verify the new firmware version is installed and confirm the password handling has been secured
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-39289 — 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-2021-39289 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