Skip to content
Fencer Vulns
high 8.2

CVE-2024-38367 in the critical feed json

CoacoaPods trunk sessions verification step could be manipulated for owner session hijacking

published 2024-07-01 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-37281

cvss
8.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
11.1%
EPSS 11.1% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

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 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.

Patch / fix

  • cocoapods trunk.cocoapods.org 2023-10-27

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

11.13% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • evasec.io https://evasec.io/blog/eva-discovered-supply-chain-vulnerabities-in-cocoapods#vulnerability-3-achieving-zero-click-account-takeover-by-defeating-email-security-boundaries referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:H
NVD 3.1 9.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

  • CocoaPods CocoaPods

Classification

Weakness
  • CWE-488 Exposure of Data Element to Wrong Session

References

Sources

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.