CVE-2023-43177
Crushftp ≤ 10.5.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-43177 is a critical-severity Improper Control of Dynamically-Managed Code Resources (CWE-913) vulnerability in Crushftp Crushftp. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Reflective Code Loading (T1620); ranked in the top 0.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CrushFTP versions prior to 10.5.1 are affected by CVE-2023-43177, an instance of Improperly Controlled Modification of Dynamically-Determined Object Attributes tracked as CWE-913. The flaw carries a CVSS 3.1 base score of 9.8 with a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating a remotely exploitable condition that can compromise confidentiality, integrity, and availability without any authentication or user interaction.
Unauthenticated attackers with network access can supply crafted input that manipulates object attributes at runtime, enabling them to achieve arbitrary code execution or full system compromise on the affected CrushFTP server.
Public references describe the issue as a zero-day disclosure and point to technical write-ups and pending GitHub disclosures that focus on the discovery timeline; the version constraint in the CVE record itself indicates that upgrading to CrushFTP 10.5.1 or later addresses the vulnerability.
The associated EPSS score reached a peak of 0.9662 and remains elevated at 0.7682, reflecting substantial post-disclosure exploitation interest that warrants renewed attention from defenders.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-47596
Vulnerability Data
CrushFTP prior to 10.5.1 is vulnerable to Improperly Controlled Modification of Dynamically-Determined Object Attributes.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
—
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requiring explicit authorization and ongoing control of mobile code implements proper management of dynamically loaded code resources.
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.
Secure SDLC practices explicitly include controls that prevent improper handling of dynamic code resources.
Blocking unauthorized code execution directly limits the ability to abuse dynamically-managed resources.
Runtime-environment monitoring can detect exploitation of the weakness but does not prevent it.
Vulnerability identification can surface instances of CWE-913 but does not mitigate the root weakness.
Hardened configuration baselines can restrict dynamic code execution and variable access at runtime.
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.
Security testing can detect dynamic code weaknesses but does not prevent them at design or coding time.
Secure development lifecycle mandates controls on dynamic code generation and resource management.
Application security requirements explicitly address restrictions on dynamic code execution and resource access.
Secure architecture principles require design controls that prevent improper dynamic code resource manipulation.
Secure coding standards directly prohibit unsafe dynamic code resource handling and injection patterns.
Environment separation reduces exposure of dynamic code resources but does not address the underlying weakness.
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).
Windows 10 (1 rule)
- V-220726 Data Execution Prevention (DEP) must be configured to at least OptOut. prevents CWE-913
Windows 11 (1 rule)
- V-253283 Data Execution Prevention (DEP) must be configured to at least OptOut. prevents CWE-913