CVE-2024-38368 in the critical feed json
Trunk's 'Claim your pod' could be used to obtain un-used pods
published 2024-07-01 2 y ago modified 2026-11-04 5 d ago also EUVD-2024-37282
- cvss
- 9.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.9%
- EPSS 14.9% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
trunk.cocoapods.org is the authentication server for the CoacoaPods dependency manager. A vulnerability affected older pods which migrated from the pre-2014 pull request workflow to trunk. If the pods had never been claimed then it was still possible to do so. It was also possible to have all owners removed from a pod, and that made the pod available for the same claiming system. This was patched server-side in commit 71be5440906b6bdfbc0bcc7f8a9fec33367ea0f4 in September 2023.
Patch / fix
- CocoaPods CocoaPods 71be5440906b6bdfbc0bcc7f8a9fec33367ea0f4
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
14.85% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:L |
| NVD | 3.1 | 9.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:L |
Affected products
- CocoaPods CocoaPods
Classification
- Weakness
-
- CWE-668 Exposure of Resource to Wrong Sphere
References
-
github.com
/CocoaPods/trunk.cocoapods.org/commit/71be5440906b6bdfbc0bcc7f8a9fec33367ea0f4
patch
-
blog.cocoapods.org
/CocoaPods-Trunk-RCEs-2023
vendor-advisory
-
github.com
/CocoaPods/CocoaPods/security/advisories/GHSA-j483-qm5c-7hqx
third-party-advisory
-
blog.cocoapods.org
/Claim-Your-Pods
product
-
evasec.webflow.io
/blog/eva-discovered-supply-chain-vulnerabities-in-cocoapods#1-taking-unauthorized-ownership-over-orphaned-pod
third-party-advisory
Sources
- CVE List CVE-2024-38368
- NVD CVE-2024-38368
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.