{"answers":{"affected":"2 open source packages ship an affected version, including namada-apps.","exploited":"There is no known exploitation of GHSA-82vg-5v4f-f9wq in the wild and no public exploit code.","fix":"Upgrade namada-apps to 1.1.0 or later.","what":"GHSA-82vg-5v4f-f9wq is a vulnerability in namada-apps, published on 20 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-82vg-5v4f-f9wq and fix it if it is affected.\n\nWhat it is: GHSA-82vg-5v4f-f9wq is a vulnerability in namada-apps, published on 20 Feb 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 GHSA-82vg-5v4f-f9wq in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- namada-apps (crates.io): affected from 1.0.0; fixed in 1.1.0\n- namada-apps (crates.io): affected from 1.0.0; fixed in 1.1.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/GHSA-82vg-5v4f-f9wq/ (Markdown: https://insights.sbomify.com/GHSA-82vg-5v4f-f9wq/index.md)","id":"GHSA-82vg-5v4f-f9wq","markdown":"https://insights.sbomify.com/GHSA-82vg-5v4f-f9wq/index.md","name":"GHSA-82vg-5v4f-f9wq","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Namada blockchain node","requires_auth":"none","summary":"A malicious transaction with many signatures causes an integer overflow, crashing the Namada node during mempool validation.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nA malicious transaction may cause a crash in mempool validation.\n\nA transaction with authorization section containing 256 public keys or more with valid matching signatures triggers an integer overflow in signature verification that causes a the node to panic.\n\n### Patches\n\nThis issue has been patched in apps version 1.1.0. The mempool validation has been fixed to avoid overflow.\n\n### Workarounds\n\nThere are no workarounds and users are advised to upgrade.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Namada-apps can Crash with Excessive Computation in Mempool Validation","id":"GHSA-82vg-5v4f-f9wq","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"integer_overflow","year":"2025"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["1.1.0"],"introduced":["1.0.0"],"last_affected":[],"package":"namada-apps","purl":null,"source":"GHSA-82vg-5v4f-f9wq"},{"ecosystem":"crates.io","fixed":["1.1.0"],"introduced":["1.0.0"],"last_affected":[],"package":"namada-apps","purl":"pkg:cargo/namada-apps","source":"GHSA-82vg-5v4f-f9wq"}],"products":null,"published":"2025-02-20","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A malicious transaction with many signatures causes an integer overflow, crashing the Namada node during mempool validation.","url":"https://insights.sbomify.com/GHSA-82vg-5v4f-f9wq/"}