{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-38367 exists.","fix":"No fix has been published for CVE-2024-38367 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-38367 is a high-severity authentication bypass vulnerability in CocoaPods, published on 1 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-38367 and fix it if it is affected.\n\nWhat it is: CVE-2024-38367 is a high-severity authentication bypass vulnerability in CocoaPods, published on 1 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-38367 exists.\n\nAffected product: CocoaPods. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-38367/ (Markdown: https://insights.sbomify.com/CVE-2024-38367/index.md)","id":"CVE-2024-38367","markdown":"https://insights.sbomify.com/CVE-2024-38367/index.md","name":"CVE-2024-38367","record":{"aliases":["GHSA-52gf-m7v9-m333"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"CocoaPods authentication server","requires_auth":"none","summary":"Attackers can hijack CocoaPods trunk sessions to take over accounts, manipulate pod specifications, and disrupt library distribution.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"trunk.cocoapods.org","vendor":"cocoapods"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-488","name":"Exposure of Data Element to Wrong Session"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"CoacoaPods trunk sessions verification step could be manipulated for owner session hijacking","id":"CVE-2024-38367","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Trunk's 'Claim your pod' could be used to obtain un-used pods","id":"CVE-2024-38368"},"packages":[],"prev":{"headline":"CoacoaPods trunk RCE in email verification system rfc-822","id":"CVE-2024-38366"},"products":["CocoaPods"],"published":"2024-07-01","related":[{"cvss_score":10,"headline":"CoacoaPods trunk RCE in email verification system rfc-822","id":"CVE-2024-38366","kev_date_added":null,"published":"2024-07-01"},{"cvss_score":9.3,"headline":"Trunk's 'Claim your pod' could be used to obtain un-used pods","id":"CVE-2024-38368","kev_date_added":null,"published":"2024-07-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-19","vendors":["CocoaPods"]},"summary":"Attackers can hijack CocoaPods trunk sessions to take over accounts, manipulate pod specifications, and disrupt library distribution.","url":"https://insights.sbomify.com/CVE-2024-38367/"}