{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25335 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25335 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25335 is a high-severity missing authorization vulnerability in n/a, published on 18 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-25335 and fix it if it is affected.\n\nWhat it is: CVE-2022-25335 is a high-severity missing authorization vulnerability in n/a, published on 18 Feb 2022. 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-2022-25335 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2022-25335/ (Markdown: https://insights.sbomify.com/CVE-2022-25335/index.md)","id":"CVE-2022-25335","markdown":"https://insights.sbomify.com/CVE-2022-25335/index.md","name":"CVE-2022-25335","record":{"aliases":["GHSA-7c5g-cjm9-2jm4"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"DeFi smart contract","requires_auth":"none","summary":"Attackers can manipulate token allowances due to missing owner-only access control in the setMultipleAllowances function.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"drago","vendor":"rigoblock"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"RigoBlock Dragos through 2022-02-17 lacks the onlyOwner modifier for setMultipleAllowances. This enables token manipulation, as exploited in the wild in February 2022. NOTE: although 2022-02-17 is the vendor's vulnerability announcement date, the vulnerability will not be remediated until a major protocol upgrade occurs.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in n/a","id":"CVE-2022-25335","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":5,"next":{"headline":"Exposure of Resource to Wrong Sphere in ezsystems/ezplatform-kernel","id":"CVE-2022-25336"},"packages":[],"prev":{"headline":"Stack overflow on SK_LOAD signature length field in Texas Instruments OMAP L138","id":"CVE-2022-25334"},"products":["n/a"],"published":"2022-02-18","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can manipulate token allowances due to missing owner-only access control in the setMultipleAllowances function.","url":"https://insights.sbomify.com/CVE-2022-25335/"}