CVE-2025-67114
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 · uneditedUse of a deterministic credential generation algorithm in /ftl/bin/calc_f2 in Small Cell Sercomm SCE4255W (FreedomFi Englewood) firmware before DG3934v3@2308041842 allows remote attackers to derive valid administrative/root credentials from the device's MAC address, enabling authentication bypass and full device access.
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 confidenceThe /ftl/bin/calc_f2 binary in Sercomm SCE4255W firmware uses a deterministic algorithm that computes administrative credentials directly from the device's MAC address. Attackers with knowledge of this algorithm can locally compute valid root/admin credentials given only the device's MAC address, achieving full authentication bypass and persistent device compromise.
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
- 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.
-
Confirm device modelIdentify the Sercomm SCE4255W device in your environment through device inventory, network scanning, or device labelsAffected if The device is a Sercomm SCE4255W unit
-
Check firmware versionAccess the device administration interface or use SNMP/telnet to retrieve the firmware version, then compare it to the fixed version DG3934v3@2308041842Affected if Firmware version is earlier than DG3934v3@2308041842 or cannot be determined
-
Verify vulnerable binary presenceAttempt to access or execute /ftl/bin/calc_f2 on the device via diagnostic shell, telnet, or SSH if availableAffected if The binary /ftl/bin/calc_f2 exists and is executable on the device
-
Assess management interface exposureReview firewall rules, ACLs, and network segmentation to determine if the device's web management or administrative interfaces are accessible from untrusted networksAffected if The management interface is exposed to untrusted or external networks
-
Verify MAC address accessibilityDetermine whether the device's MAC address is discoverable through ARP tables, network scanning, or physical access to the device labelAffected if The MAC address can be obtained by an attacker on the same network segment
A user is affected if they operate a Sercomm SCE4255W device running firmware older than DG3934v3@2308041842 with the /ftl/bin/calc_f2 binary present and the management interface or MAC address exposed to untrusted parties.
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.
From vendor dataApply vendor firmware update DG3934v3@2308041842 or later to replace the deterministic credential generation. Until patched, strictly limit exposure of the device's management interface to trusted networks and monitor for unauthorized access attempts.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67114 — 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-67114 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