{"answers":{"affected":"2 open source packages ship an affected version, including orml-rewards.","exploited":"There is no known exploitation of GHSA-5v93-9mqw-p9mh in the wild and no public exploit code.","fix":"Upgrade orml-rewards to 1.2.1 or later.","what":"GHSA-5v93-9mqw-p9mh is a vulnerability in orml-rewards, published on 14 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-5v93-9mqw-p9mh and fix it if it is affected.\n\nWhat it is: GHSA-5v93-9mqw-p9mh is a vulnerability in orml-rewards, published on 14 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-5v93-9mqw-p9mh in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- orml-rewards (crates.io): affected all versions; fixed in 1.2.1\n- orml-rewards (crates.io): affected all versions; fixed in 1.2.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/GHSA-5v93-9mqw-p9mh/ (Markdown: https://insights.sbomify.com/GHSA-5v93-9mqw-p9mh/index.md)","id":"GHSA-5v93-9mqw-p9mh","markdown":"https://insights.sbomify.com/GHSA-5v93-9mqw-p9mh/index.md","name":"GHSA-5v93-9mqw-p9mh","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Substrate runtime library","requires_auth":"low_privilege","summary":"An integer overflow in the ORML Rewards pallet allows attackers to crash nodes via crafted inputs, requiring a patch update.","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":"## Summary\nA vulnerability in the `add_share` function of the **Rewards** pallet (part of the ORML repository) can lead to an uncaught Rust panic when handling user-provided input exceeding the `u128` range.\n\n## Affected Components\n- **ORML Rewards** pallet (`rewards/src/lib.rs`)\n- Any Substrate-based chain using ORML Rewards with `add_share` accepting unvalidated large `u128` inputs\n\n## Technical Details\n- `add_share` performs arithmetic on user-supplied values (`add_amount`) of type `T::Share` (mapped to `u128` in Acala).\n- If `add_amount` is large enough (e.g., `i128::MAX`), the intermediate result may overflow and panic on the cast to `u128`.\n- Validation occurs only after arithmetic, enabling a crafted input to trigger an overflow.\n\n## Impact\nA malicious user submitting a specially crafted extrinsic can cause a panic in the runtime:\n- **Denial of Service** by crashing the node process.\n- **Potential for invalid blocks** produced by validators.\n\n## Likelihood\nThis issue is exploitable in production if there exists at least one rewards pool where reward tokens exceed twice the collateral tokens, allowing sufficiently large multiplication to exceed `u128` bounds.\n\n## Remediation\n- This issue is fixed in https://github.com/open-web3-stack/open-runtime-module-library/pull/1016\n\n## Backport\n\nThe patch have been backported to following release branches:\n- polkadot-stable2407\n- polkadot-stable2409\n\nA 1.0.1 patch release is made with this fix.","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":"Uncaught Panic in ORML Rewards Pallet","id":"GHSA-5v93-9mqw-p9mh","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.2.1"],"introduced":["0"],"last_affected":[],"package":"orml-rewards","purl":null,"source":"GHSA-5v93-9mqw-p9mh"},{"ecosystem":"crates.io","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"orml-rewards","purl":"pkg:cargo/orml-rewards","source":"GHSA-5v93-9mqw-p9mh"}],"products":null,"published":"2025-02-14","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":"An integer overflow in the ORML Rewards pallet allows attackers to crash nodes via crafted inputs, requiring a patch update.","url":"https://insights.sbomify.com/GHSA-5v93-9mqw-p9mh/"}