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:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
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, 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
CVEs Like This One
Affected Assets
Mitigating Controls
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 (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.25 mandates secure SDLC practices (secure coding guidelines, security requirements, checkpoints, testing, developer training and capability) that reach improper control of dynamic code resources when they manifest as injection, insecure deserialization or logic flaws in first-party code; this stops exploitation for that slice but leaves a bounded remainder (e.g. third-party libraries, runtime configuration, or outsourced development that evades the org's rules)
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.
Security testing can detect dynamic code weaknesses but does not prevent them at design or coding time.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-913, a class-level weakness, and none of its children carries one either.