{"answers":{"affected":"2 open source packages ship an affected version, including laravel/reverb.","exploited":"There is no known exploitation of CVE-2024-50347 in the wild and no public exploit code.","fix":"Upgrade laravel/reverb to 1.4.0 or later.","what":"CVE-2024-50347 is a medium-severity missing authorization vulnerability in laravel reverb, published on 31 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-50347 and fix it if it is affected.\n\nWhat it is: CVE-2024-50347 is a medium-severity missing authorization vulnerability in laravel reverb, published on 31 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-50347 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- laravel/reverb (Packagist): affected all versions; fixed in 1.4.0\n- laravel/reverb (Packagist): affected all versions; fixed in 1.4.0\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-50347/ (Markdown: https://insights.sbomify.com/CVE-2024-50347/index.md)","id":"CVE-2024-50347","markdown":"https://insights.sbomify.com/CVE-2024-50347/index.md","name":"CVE-2024-50347","record":{"aliases":["GHSA-pfrr-xvrf-pxjx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel Reverb","requires_auth":"none","summary":"Attackers can bypass API signature verification to broadcast messages or read channel statistics if the application ID is known.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/U:Green","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Laravel Reverb provides a real-time WebSocket communication backend for Laravel applications. Prior to 1.4.0, there is an issue where verification signatures for requests sent to Reverb's Pusher-compatible API were not being verified. This API is used in scenarios such as broadcasting a message from a backend service or for obtaining statistical information (such as number of connections) about a given channel. This issue only affects the Pusher-compatible API endpoints and not the WebSocket connections themselves. In order to exploit this vulnerability, the application ID which, should never be exposed, would need to be known by an attacker. This vulnerability is fixed in 1.4.0.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Laravel Reverb has Missing API Signature Verification","id":"CVE-2024-50347","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":2,"n_references":4,"next":{"headline":"InstantCMS has a Cross Site Scripting Vulnerability","id":"CVE-2024-50348"},"packages":[{"ecosystem":"Packagist","fixed":["1.4.0"],"introduced":["0"],"last_affected":[],"package":"laravel/reverb","purl":null,"source":"GHSA-pfrr-xvrf-pxjx"},{"ecosystem":"Packagist","fixed":["1.4.0"],"introduced":["0"],"last_affected":[],"package":"laravel/reverb","purl":"pkg:composer/laravel/reverb","source":"GHSA-pfrr-xvrf-pxjx"}],"prev":{"headline":"WebFeed HTML injection vulnerabilities","id":"CVE-2024-50346"},"products":["reverb"],"published":"2024-10-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-31","vendors":["laravel"]},"summary":"Attackers can bypass API signature verification to broadcast messages or read channel statistics if the application ID is known.","url":"https://insights.sbomify.com/CVE-2024-50347/"}