Cyber Resilience

CVE-2024-9643

Exposed Creds in Four-Faith F3X36 Firmware 2.0

Public PoCExposed Creds
Published
04 February 2025
Modified
19 September 2025
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.030 86th percentile
Risk Priority 89 floored blend · peak EPSS

Summary

CVE-2024-9643 is a critical-severity Active Debug Code (CWE-489) vulnerability in Four-Faith F3X36 Firmware. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked in the top 14% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The Four-Faith F3x36 router running firmware version 2.0.0 is affected by an authentication bypass vulnerability in its administrative web server. The issue stems from hard-coded credentials (CWE-798) combined with active debug code exposure (CWE-489), allowing remote attackers to bypass normal login controls. The flaw carries a CVSS 3.1 score of 9.8 and is noted as similar to the earlier CVE-2023-32645.

An unauthenticated attacker with knowledge of the embedded credentials can submit specially crafted HTTP requests to the web interface and obtain full administrative control over the device. No user interaction or prior authentication is required, enabling complete compromise of confidentiality, integrity, and availability.

Public advisories from Talos and VulnCheck detail the hard-coded credential issue and reference the related TALOS-2023-1752 report, though no specific patch or firmware remediation steps are described in the available references.

EPSS scores for the CVE rose from lower values to a peak of 0.3857 on 2026-03-15 before receding to the current 0.1818, indicating a period of increased exploitation interest after disclosure.

OWASP Top 10 for Web (2025)

A02:2025 Security MisconfigurationA07:2025 Authentication Failures

EU & UK References

Vulnerability Data

The Four-Faith F3x36 router using firmware v2.0.0 is vulnerable to authentication bypass due to hard-coded credentials in the administrative web server. An attacker with knowledge of the credentials can gain administrative access via crafted HTTP requests. This issue appears similar…

more

to CVE-2023-32645.

CWE(s)
CWE-489CWE-798

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
attack.mitre.org →
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
attack.mitre.org →
T1078.001 Default Accounts Stealth
Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1552.004 Private Keys Credential Access
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-9644Same product: Four-Faith F3X36
CVE-2024-12856Same product: Four-Faith F3X36
CVE-2025-10709Same vendor: Four-Faith
CVE-2025-11018Same vendor: Four-Faith
CVE-2025-10708Same vendor: Four-Faith
CVE-2023-6308Same vendor: Four-Faith
CVE-2023-3805Same vendor: Four-Faith
CVE-2024-27107Shared CWE-798
CVE-2024-8135Shared CWE-798
CVE-2023-40463Shared CWE-798

Affected Assets

four-faith
f3x36 firmware
2.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

IA-5 Authenticator Management good match

Authenticator management requires secure distribution and handling of credentials, structurally discouraging hard-coded values.

SC-12 Cryptographic Key Establishment and Management good match

Cryptographic key management mandates proper establishment and handling instead of embedding keys in code.

CM-2 Baseline Configuration partial match

Baseline configuration defines the approved production state that must exclude active debug code.

CM-7 Least Functionality partial match

Least functionality explicitly prohibits enabling unnecessary debug or diagnostic features in production builds.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and tools can require removal of debug code before release.

SA-3 System Development Life Cycle partial match

Security-integrated SDLC processes ensure debug artifacts are stripped prior to deployment.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.

PR.AA-01 partial match
prevents

PR.AA-01's credential/key-management processes can reduce the incentive to embed secrets but do not address or detect hard-coded values in source code, so the weakness remains fully possible.

PR.AA-02 none match
prevents

PR.AA-02 addresses human identity proofing and per-person credential issuance at enrollment; it has no bearing on whether developers embed static credentials in software.

PR.DS-01 none match
prevents

PR.DS-01 addresses encryption and integrity of stored data but never touches credential or key management practices, so it neither prevents hard-coded credentials nor removes any of their risk.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance catches active debug code before deployment.

A.8.9 Configuration management mostly match
prevents

Configuration management can disable or remove debug features through hardened baselines.

A.6.3 Information security awareness, education and training partial match
prevents

Education on secure configuration practices discourages technical staff from embedding or relying on hard-coded credentials in systems and applications.

A.8.24 Use of cryptography partial match
mitigates

Secure key-generation, distribution and storage procedures reduce the likelihood that hard-coded or default cryptographic keys will be introduced or left unprotected.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates removal of debug code before release.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly prohibit leaving debug code active in production.

References