CVE-2024-38367
Trunk.Cocoapods.Org ≤ 2023-10-27
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:HSummary
CVE-2024-38367 is a high-severity Exposure of Data Element to Wrong Session (CWE-488) vulnerability in Cocoapods Trunk.Cocoapods.Org. Its CVSS base score is 8.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Web Session Cookie (T1550.004); ranked in the top 4% 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 AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — 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-38367 affects trunk.cocoapods.org, the authentication server for the CocoaPods dependency manager. Prior to commit d4fa66f49cedab449af9a56a21ab40697b9f7b97, a flaw in the trunk sessions verification step allowed manipulation that enabled owner session hijacking. The issue is tracked under CWE-488 with a CVSS 3.1 score of 8.2.
An unauthenticated remote attacker can exploit the weakness by manipulating session verification to hijack a victim's CocoaPods trunk session. Successful compromise grants full control of the account, permitting the attacker to alter pod specifications, interfere with legitimate library distribution, or trigger broader disruption across the CocoaPods ecosystem.
The vulnerability was addressed server-side by the referenced commit deployed in October 2023. Public advisories and the CocoaPods security notice direct administrators to ensure their environments rely on the patched trunk.cocoapods.org instance; no client-side changes are required.
EPSS scores remain low, with a current value of 0.0499 and a peak of 0.0512.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-37281
Vulnerability Data
trunk.cocoapods.org is the authentication server for the CoacoaPods dependency manager. Prior to commit d4fa66f49cedab449af9a56a21ab40697b9f7b97, the trunk sessions verification step could be manipulated for owner session hijacking Compromising a victim’s session will result in a full takeover of the CocoaPods trunk…
more
account. The threat actor could manipulate their pod specifications, disrupt the distribution of legitimate libraries, or cause widespread disruption within the CocoaPods ecosystem. This was patched server-side with commit d4fa66f49cedab449af9a56a21ab40697b9f7b97 in October 2023.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 enforces access decisions that can be scoped to the correct session context.
AC-4 controls information flows between entities, reducing cross-session leakage.
SC-4 directly stops unintended transfer of data through shared resources that different sessions may access.
SC-39 isolates execution domains so one session cannot reach another's state or data.
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.
Enforcing authorization policies and least privilege can prevent cross-session data exposure when session separation is treated as an access rule.
Protecting data-in-use directly addresses runtime leakage of session data to unauthorized contexts.
Logical access controls and segmentation can be applied to isolate session state within applications or environments.
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 the weakness but does not itself implement the preventive control.
Secure development lifecycle practices include session-management controls that prevent exposure of data to the wrong session.
Application security requirements explicitly call for proper session isolation and state management.
Secure system architecture principles require isolation of session state to avoid cross-session data leakage.
Secure coding standards mandate correct session handling to prevent exposure of data elements to the wrong session.
Information access restriction directly enforces session boundaries so data is not exposed to the wrong session.