CVE-2024-9644
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 · uneditedThe Four-Faith F3x36 router using firmware v2.0.0 is vulnerable to an authentication bypass vulnerability in the administrative web server. Authentication is not enforced on some administrative functionality when using the "bapply.cgi" endpoint instead of the normal "apply.cgi" endpoint. A remote and unauthenticated can use this vulnerability to modify settings or chain with existing authenticated vulnerabilities.
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 Four-Faith F3x36 router firmware v2.0.0 contains an authentication bypass in the web administrative interface. The 'bapply.cgi' endpoint fails to enforce authentication checks that are properly implemented on the standard 'apply.cgi' endpoint, allowing unauthenticated remote attackers to access administrative functionality and modify router settings.
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= 2.0CVSS 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 router model and firmware versionAccess the router's web administrative interface and navigate to the status or system information page to view the firmware version. Alternatively, check the device label or documentation for the model number.Affected if The router is a Four-Faith F3x36 running firmware version 2.0.0
-
Check if bapply.cgi accepts unauthenticated requestsAttempt to access http://<router-ip>/bapply.cgi directly from a browser without logging in or in an incognito window. Compare the response to accessing /apply.cgi without authentication, which should redirect to a login page.Affected if The bapply.cgi endpoint returns a valid response or configuration options without requiring authentication, while apply.cgi properly enforces authentication by redirecting to a login page
-
Verify network exposure of the administrative interfaceDetermine if the router's web management port (typically HTTP port 80 or HTTPS port 443) is accessible from untrusted networks by checking firewall rules, WAN interface bindings, or using external network scanning tools.Affected if The router's administrative web interface is exposed to the WAN or other untrusted networks, making the authentication bypass exploitable remotely
A user is affected if they have a Four-Faith F3x36 router running firmware version 2.0.0 where the bapply.cgi endpoint can be accessed without authentication while the standard apply.cgi endpoint properly enforces authentication.
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 dataRestrict external access to the router's administrative web interface via firewall rules or ACLs until a vendor firmware patch is available; if the administrative interface must be accessible, implement additional authentication controls at the network layer.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9644 — 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-2024-9644 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