CVE-2025-44652
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 RAX30 V1.0.10.94_3, the USERLIMIT_GLOBAL option is set to 0 in multiple bftpd-related configuration files. 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 · high confidenceIn Netgear RAX30 firmware V1.0.10.94_3, the bftpd FTP server configuration files have USERLIMIT_GLOBAL set to 0, which disables the global user connection limit. This allows unlimited concurrent FTP connections, enabling attackers to exhaust server resources and cause 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.0.10.94_3CVSS 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 the device modelAccess the router web interface or SSH and confirm the model is Netgear RAX30Affected if Device is not a Netgear RAX30, then not affected by this specific CVE
-
Check the firmware versionIn the router web interface under Firmware Update or via CLI, verify the installed firmware version is exactly 1.0.10.94_3Affected if Firmware version is 1.0.10.94_3 - this is the only affected version per the CVE
-
Verify bftpd FTP server is enabledCheck if the FTP server feature is enabled in the router web interface under USB Storage or FTP settings, or run 'ps | grep bftpd' via SSHAffected if bftpd is not enabled or not running - the vulnerability only applies when the FTP server is active
-
Inspect bftpd configuration for USERLIMIT_GLOBALAccess the router via SSH and locate the bftpd configuration file (typically in /etc or /tmp), then search for USERLIMIT_GLOBAL settingAffected if USERLIMIT_GLOBAL is set to 0 - this indicates the vulnerable configuration allowing unlimited connections
You are affected if you have a Netgear RAX30 running firmware 1.0.10.94_3 with the bftpd FTP server enabled and USERLIMIT_GLOBAL=0 in the configuration.
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 dataWait for Netgear to release a firmware update that sets USERLIMIT_GLOBAL to an appropriate non-zero value, or disable the bftpd service if not required.
- Consultation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-44652 — 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-44652 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