CVE-2025-44650
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 · uneditedIn Netgear R7000 V1.3.1.64_10.1.36 and EAX80 V1.0.1.70_1.0.2, the USERLIMIT_GLOBAL option is set to 0 in the bftpd.conf configuration file. This can cause DoS attacks when unlimited users are connected.
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 confidenceIn Netgear R7000 and EAX80 firmware versions, the bftpd FTP server configuration file (bftpd.conf) has USERLIMIT_GLOBAL set to 0, which removes all limits on concurrent user connections. This misconfiguration allows an attacker to open unlimited simultaneous connections and exhaust server resources, resulting in a denial of service.
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.3.1.64_10.1.36= 1.0.1.70_1.0.2CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 router modelCheck the device model label or admin interface to confirm it is a Netgear R7000 or EAX80 routerAffected if Device is not a Netgear R7000 or EAX80, then not affected by this specific CVE
-
Check firmware versionAccess the router admin web interface (typically at 192.168.1.1) and navigate to the Firmware Update or Administration section to view the current firmware versionAffected if Firmware version is not exactly 1.3.1.64_10.1.36 for R7000 or 1.0.1.70_1.0.2 for EAX80, then not affected
-
Verify bftpd FTP server is enabledIn the router admin interface, look for FTP server, file sharing, or port forwarding settings to determine if the built-in FTP server (bftpd) is turned onAffected if bftpd FTP server is disabled, then the misconfiguration cannot be exploited
-
Inspect bftpd.conf for USERLIMIT_GLOBAL settingAccess the router via telnet or SSH (if enabled), or extract the firmware image and locate the bftpd.conf configuration file. Search for the line containing USERLIMIT_GLOBAL and note its valueAffected if USERLIMIT_GLOBAL is set to 0 (zero), the router is vulnerable to resource exhaustion from unlimited concurrent connections
A router is affected only if it is a Netgear R7000 running firmware 1.3.1.64_10.1.36 or EAX80 running 1.0.1.70_1.0.2, has bftpd FTP server enabled, and the bftpd.conf file has USERLIMIT_GLOBAL set to 0.
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 dataModify the bftpd.conf configuration file to set USERLIMIT_GLOBAL to a reasonable maximum value (e.g., 10-50) based on expected legitimate usage, then restart the bftpd service.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-44650 — 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-44650 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