CVE-2024-38366
Trunk.Cocoapods.Org ≤ 2023-09-22
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-38366 is a critical-severity Injection (CWE-74) vulnerability in Cocoapods Trunk.Cocoapods.Org. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 3% 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 SI-10 (Information Input Validation) — 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-38366 is a remote code execution vulnerability in trunk.cocoapods.org, the authentication server for the CocoaPods dependency manager. The affected component is the email verification logic used during user signup, which relied on an rfc-822 library that performed DNS MX record validation by executing a shell command; improper handling of the lookup response allowed command injection (CWE-74). The issue carried a CVSS 3.1 score of 10.0.
An unauthenticated attacker could exploit the flaw by manipulating the DNS MX response during email verification to execute arbitrary commands on the trunk server, obtaining root-level access to the infrastructure. Successful exploitation would let the attacker modify any Podspec stored in trunk and would have enabled supply-chain compromise of CocoaPods users; the incident resulted in a full user-session reset after discovery.
The vulnerability was fixed server-side in September 2023 via commit 001cc3a430e75a16307f5fd6cdff1363ad2f40f3. Public advisories and the CocoaPods security announcement describe the root cause and confirm the patch was applied before the CVE publication date. The associated EPSS score rose from a low baseline to a peak of 0.59, indicating emerging exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-37280
Vulnerability Data
trunk.cocoapods.org is the authentication server for the CoacoaPods dependency manager. The part of trunk which verifies whether a user has a real email address on signup used a rfc-822 library which executes a shell command to validate the email domain…
more
MX records validity. It works via an DNS MX. This lookup could be manipulated to also execute a command on the trunk server, effectively giving root access to the server and the infrastructure. This issue was patched server-side with commit 001cc3a430e75a16307f5fd6cdff1363ad2f40f3 in September 2023. This RCE triggered a full user-session reset, as an attacker could have used this method to write to any Podspec in trunk.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.1V1.2.3V1.2.5V1.2.8
Mitigating Controls (NIST 800-53 r5) AI
SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.
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 directly require input validation and output encoding that prevent injection flaws.
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 in development catches injection vulnerabilities before release.
Logging supports detection of injection attempts but does not prevent the weakness.
Monitoring activities can identify active injection attacks after they occur.
Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.
Application security requirements explicitly call for controls against injection attacks in software design.
Secure architecture principles reduce injection surfaces but do not prescribe specific neutralization techniques.