{"answers":{"affected":"3 open source packages ship an affected version, including github.com/quic-go/quic-go.","exploited":"There is no known exploitation of CVE-2025-29785 in the wild and no public exploit code.","fix":"Upgrade github.com/quic-go/quic-go to 0.50.1 or later.","what":"CVE-2025-29785 is a high-severity vulnerability in quic-go, published on 2 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-29785 and fix it if it is affected.\n\nWhat it is: CVE-2025-29785 is a high-severity vulnerability in quic-go, published on 2 Jun 2025. 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-2025-29785 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/quic-go/quic-go (Go): affected from 0.50.0; fixed in 0.50.1\n- github.com/quic-go/quic-go (Go): affected from 0.50.0; fixed in 0.50.1\n- github.com/quic-go/quic-go (Go): affected from 0.50.0; fixed in 0.50.1\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-2025-29785/ (Markdown: https://insights.sbomify.com/CVE-2025-29785/index.md)","id":"CVE-2025-29785","markdown":"https://insights.sbomify.com/CVE-2025-29785/index.md","name":"CVE-2025-29785","record":{"aliases":["DEBIAN-CVE-2025-29785","GHSA-j972-j939-p2v3","GO-2025-3735","UBUNTU-CVE-2025-29785"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Go QUIC library","requires_auth":"none","summary":"A malicious QUIC client can trigger a nil-pointer dereference in quic-go, causing a denial of service via crafted path probe acknowledgments.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-248","name":"Uncaught Exception"}],"description":"quic-go is an implementation of the QUIC protocol in Go. The loss recovery logic for path probe packets that was added in the v0.50.0 release can be used to trigger a nil-pointer dereference by a malicious QUIC client. In order to do so, the attacker first sends valid QUIC packets from different remote addresses (thereby triggering the newly added path validation logic: the server sends path probe packets), and then sending ACKs for packets received from the server specifically crafted to trigger the nil-pointer dereference. v0.50.1 contains a patch that fixes the vulnerability. This release contains a test that generates random sequences of sent packets (both regular and path probe packets), that was used to verify that the patch actually covers all corner cases. No known workarounds are available.","ecosystems":["Go"],"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":"quic-go Has Panic in Path Probe Loss Recovery Handling","id":"CVE-2025-29785","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"Memory Exhaustion in Expr Parser with Unrestricted Input","id":"CVE-2025-29786"},"packages":[{"ecosystem":"Go","fixed":["0.50.1"],"introduced":["0.50.0"],"last_affected":[],"package":"github.com/quic-go/quic-go","purl":null,"source":"GHSA-j972-j939-p2v3"},{"ecosystem":"Go","fixed":["0.50.1"],"introduced":["0.50.0"],"last_affected":[],"package":"github.com/quic-go/quic-go","purl":"pkg:golang/github.com/quic-go/quic-go","source":"GHSA-j972-j939-p2v3"},{"ecosystem":"Go","fixed":["0.50.1"],"introduced":["0.50.0"],"last_affected":[],"package":"github.com/quic-go/quic-go","purl":"pkg:golang/github.com/quic-go/quic-go","source":"GO-2025-3735"}],"prev":{"headline":"NamelessMC Has Lack of Length Validation for s Parameter in GET Requests","id":"CVE-2025-29784"},"products":["quic-go"],"published":"2025-06-02","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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-02","vendors":["quic-go"]},"summary":"A malicious QUIC client can trigger a nil-pointer dereference in quic-go, causing a denial of service via crafted path probe acknowledgments.","url":"https://insights.sbomify.com/CVE-2025-29785/"}