CVE-2025-50401
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 · uneditedMercury D196G d196gv1-cn-up_2020-01-09_11.21.44 is vulnerable to Buffer Overflow in the function sub_404CAEDC via the parameter password.
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 · moderate confidenceBuffer overflow vulnerability in Mercury D196G router firmware (version d196gv1-cn-up_2020-01-09_11.21.44) in function sub_404CAEDC, allowing remote code execution via an overly long password parameter sent to the web management interface.
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 dataall versionsCVSS 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 the router modelCheck the device label, web interface status page, or administrative console for the exact model number. Confirm it is a Mercurycom D196G or D196g device.Affected if The device model is Mercurycom D196g or D196gv1
-
Determine the firmware versionAccess the router web management interface and navigate to the System or Status section to view the firmware version. Alternatively, check the firmware file name if you have access to it (common naming pattern: d196gv1-cn-up_YYYY-MM-DD_HH.MMSS).Affected if The firmware version matches d196gv1-cn-up_2020-01-09_11.21.44 or is any other version of this firmware line
-
Check web management interface exposureDetermine if the router web management interface (typically on ports 80 or 443) is accessible from untrusted network segments such as the internet or guest networks. Use a port scan from an external host or review firewall rules.Affected if The web management interface is reachable from outside the trusted local network
-
Verify the vulnerable function existsIf you have access to the firmware binary, search for the string 'sub_404CAEDC' or analyze the web server binary for the password handling routine. In the live device, this requires firmware analysis.Affected if The firmware contains the function sub_404CAEDC handling password parameters (firmware analysis required)
-
Assess network accessibility to management portReview router firewall settings and any upstream network devices to confirm whether TCP ports used for web management (80/443) are open to untrusted interfaces.Affected if Ports 80 or 443 on the router are accessible from untrusted network segments
If the device is a Mercurycom D196G router running any version of its firmware and the web management interface is accessible from untrusted networks, the device is affected by this vulnerability.
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 patch when available; immediately restrict network access to the router's management interface using firewall rules or network segmentation as compensating controls until patch is deployed.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50401 — 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-50401 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