dbcve.org
CWE-321Weakness · CWE-321

CVE-2025-67112

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Use of a hard-coded AES-256-CBC key in the configuration backup/restore implementation of Small Cell Sercomm SCE4255W (FreedomFi Englewood) firmware before DG3934v3@2308041842 allows remote authenticated users to decrypt, modify, and re-encrypt device configurations, enabling credential manipulation and privilege escalation via the GUI import/export functions.

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 confidence

The Small Cell Sercomm SCE4255W firmware uses a hard-coded AES-256-CBC key in its configuration backup/restore mechanism. This allows any authenticated remote user to decrypt existing device configurations, modify them (including credentials), and re-encrypt them for re-import, enabling privilege escalation through the GUI import/export functions.

MitigationUpdate firmware to version DG3934v3@2308041842 or later to replace the hard-coded key with a securely generated one. If immediate patching is not possible, restrict access to the configuration backup/restore functions and monitor for unauthorized configuration imports.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device web interface or CLI and retrieve the model identifier. Look for 'SCE4255W' or 'Sercomm SCE4255W' in the device information page or system status.
    Affected if The device model is Sercomm SCE4255W and the firmware version is below DG3934v3@2308041842
  2. Retrieve the firmware version
    Navigate to the device's web GUI status page or use CLI command 'show version' or 'system info' to obtain the installed firmware version string.
    Affected if The firmware version is earlier than DG3934v3@2308041842 (the fixed release)
  3. Confirm backup/restore feature access
    Log into the device web interface and locate the configuration backup/restore or import/export functions, typically under 'Maintenance', 'System', or 'Administration' menus.
    Affected if The backup/restore configuration feature is accessible with authenticated access
  4. Inspect configuration files for hardcoded keys
    Download a configuration backup file (if available) and examine it using a hex editor or text viewer. Look for consistent 32-byte (256-bit) hex strings that appear across multiple backup files, which may indicate a hardcoded AES-256-CBC key.
    Affected if The same AES key value appears identically in multiple configuration backups or can be extracted from firmware images

You are affected if you are running Sercomm SCE4255W firmware versions before DG3934v3@2308041842 and have the configuration backup/restore feature accessible to authenticated users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update firmware to version DG3934v3@2308041842 or later to replace the hard-coded key with a securely generated one. If immediate patching is not possible, restrict access to the configuration backup/restore functions and monitor for unauthorized configuration imports.

Recommended fix High confidence

DG3934v3@2308041842 or later

  1. Check current firmware version via the device's admin GUI or CLI (e.g., 'show version' or System > Status).
  2. Confirm the installed version is earlier than DG3934v3@2308041842; if so, the device is affected by CVE-2025-67112.
  3. Download the patched firmware image DG3934v3@2308041842 (or a later version) from the official vendor (FreedomFi, Sercomm, or your carrier) support site.
  4. Verify the integrity of the downloaded firmware using the vendor-provided SHA256 checksum.
  5. Log into the device's administrative interface (web GUI or SSH) and navigate to the firmware upgrade or system update section.
  6. Upload the new firmware image and initiate the upgrade; allow the device to reboot automatically.
  7. After reboot, verify the new firmware version is DG3934v3@2308041842 or later.
  8. Generate a fresh configuration backup via the GUI and confirm that the encryption key has changed (the backup file should not be decryptable with the hard‑coded AES‑256‑CBC key).
Caveat Review the release notes for any configuration or UI changes; a firmware upgrade may require re‑provisioning or re‑import of the configuration.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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