CVE-2024-48886
Fortinet Fortiproxy 2.0.0 – 2.0.15
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-48886 is a critical-severity Weak Authentication (CWE-1390) vulnerability in Fortinet Fortiproxy. Its CVSS base score is 9.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-12 (Identity Proofing) and IA-2 (Identification and Authentication (Organizational Users)) — 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.
CVE-2024-48886 is a weak authentication vulnerability present in several Fortinet products, including FortiOS versions 7.4.0 through 7.4.4, 7.2.0 through 7.2.8, 7.0.0 through 7.0.15, and 6.4.0 through 6.4.15; FortiProxy versions 7.4.0 through 7.4.4, 7.2.0 through 7.2.10, 7.0.0 through 7.0.17, and 2.0.0 through 2.0.14; FortiManager versions 7.6.0 through 7.6.1 and 7.4.1 through 7.4.3; FortiManager Cloud versions 7.4.1 through 7.4.3; and FortiAnalyzer Cloud versions 7.4.1 through 7.4.3. The flaw, associated with CWE-1390 and NVD-CWE-Other, enables attackers to execute unauthorized code or commands through a brute-force attack. It carries a CVSS v3.1 base score of 9.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H).
A remote, unauthenticated attacker can exploit this vulnerability over the network by performing a brute-force attack, which requires high attack complexity but no user interaction. Successful exploitation grants the attacker the ability to execute arbitrary code or commands on the affected system, potentially leading to full compromise given the high impacts on confidentiality, integrity, availability, and changed scope.
Mitigation details and patches are outlined in the Fortinet PSIRT advisory available at https://fortiguard.fortinet.com/psirt/FG-IR-24-221. Security practitioners should consult this reference for version-specific remediation guidance.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-43226
Vulnerability Data
A weak authentication in Fortinet FortiOS versions 7.4.0 through 7.4.4, 7.2.0 through 7.2.8, 7.0.0 through 7.0.15, 6.4.0 through 6.4.15, FortiProxy versions 7.4.0 through 7.4.4, 7.2.0 through 7.2.10, 7.0.0 through 7.0.17, 2.0.0 through 2.0.14, FortiManager versions 7.6.0 through 7.6.1, 7.4.1 through…
more
7.4.3, FortiManager Cloud versions 7.4.1 through 7.4.3, FortiAnalyzer Cloud versions 7.4.1 through 7.4.3 allows attacker to execute unauthorized code or commands via a brute-force attack.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 9 hardening rules · 7 OS baselines
V7.6.1V6.3.6V6.4.2V6.4.4
Mitigating Controls (NIST 800-53 r5) AI
Requires identity proofing at appropriate assurance levels before granting accounts, directly addressing insufficient proof of identity.
Requires unique identification and authentication of users, directly stopping weak mechanisms from being used.
Requires device identification and authentication before establishing connections.
Extends strong identification and authentication requirements to non-organizational users.
Mandates proper authenticator issuance, management, and strength to ensure claimed identities are verified.
Enforces access decisions based on authenticated identities, making weak authentication less exploitable.
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.
Explicitly requires authentication of users/services/hardware with MFA and password-strength controls.
Identity proofing and binding is a core prerequisite for non-weak authentication.
Credential management directly supports stronger authentication but does not guarantee proof of identity.
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.
Mandating multi-factor and non-password authentication techniques counters the use of inherently weak single-factor or password-only authentication mechanisms.
Strong-password and non-reuse requirements raise the bar against weak single-factor authentication that can be exploited via guessing or credential stuffing.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-1390
RHEL 7 (1 rule)
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. prevents CWE-1390
RHEL 8 (1 rule)
- V-230492 RHEL 8 must not have the rsh-server package installed. prevents CWE-1390
Ubuntu 22.04 (1 rule)
- V-260470 Ubuntu 22.04 LTS, when booted, must require authentication upon booting into single-user and maintenance modes. prevents CWE-1390
Windows 10 (1 rule)
- V-220865 The Windows Remote Management (WinRM) service must not use Basic authentication. prevents CWE-1390
Windows 11 (1 rule)
- V-253418 The Windows Remote Management (WinRM) service must not use Basic authentication. prevents CWE-1390