CVE-2024-12777
Aimstack Aim 3.25.0
Raw vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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-2024-12777 is a medium-severity Synchronous Access of Remote Resource without Timeout (CWE-1088) vulnerability in Aimstack Aim. Its CVSS base score is 5.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 40th percentile by exploit likelihood (below the median); 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 SC-10 (Network Disconnect) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6999
Vulnerability Data
A vulnerability in aimhubio/aim version 3.25.0 allows for a denial of service through the misuse of the sshfs-client. The tracking server, which is single-threaded, can be made unresponsive by requesting it to connect to an unresponsive socket via sshfs. The…
more
lack of an additional timeout setting in the sshfs-client causes the server to hang for a significant amount of time, preventing it from responding to other requests.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SC-10 requires terminating network connections after a defined period, directly enforcing timeouts on remote synchronous calls.
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.
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.
Redundancy and failover mechanisms can mitigate the impact of a hung synchronous call but do not enforce timeouts.
Network security controls can include connection-timeout policies, yet the weakness is a coding-level omission.
Secure SDLC practices require timeout handling for external calls, directly addressing the missing timeout.
Application security requirements typically mandate timeout settings for remote resource access.
A.8.27 establishes and applies secure-by-design principles (defense-in-depth, least privilege, fail securely, distrust external input, zero-trust verification) during architecture and engineering; it does not stop a synchronous remote call without timeout from being written or from blocking when it occurs.