{"answers":{"affected":"3 open source packages ship an affected version, including chia-blockchain. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36447 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36447 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36447 is a high-severity vulnerability in n/a, published on 29 Jul 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-36447 and fix it if it is affected.\n\nWhat it is: CVE-2022-36447 is a high-severity vulnerability in n/a, published on 29 Jul 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-36447 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- chia-blockchain (PyPI): affected all versions up to 2.4.4rc3; no fix listed\n- chia-blockchain (PyPI): affected all versions up to 2.4.4rc3; no fix listed\n- chia-blockchain (PyPI): affected all versions up to 2.4.4rc3; no fix listed\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-36447/ (Markdown: https://insights.sbomify.com/CVE-2022-36447/index.md)","id":"CVE-2022-36447","markdown":"https://insights.sbomify.com/CVE-2022-36447/index.md","name":"CVE-2022-36447","record":{"aliases":["GHSA-pvjg-jwp3-mrj5","PYSEC-2022-43072"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Chia blockchain CAT1","requires_auth":"none","summary":"Any holder of a Chia CAT1 token can arbitrarily inflate the total supply, compromising the token's economic integrity and requiring off-chain mitigation.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"network_cat1_standard","vendor":"chia"}],"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":[],"description":"An inflation issue was discovered in Chia Network CAT1 Standard 1.0.0. Previously minted tokens minted on the Chia blockchain using the CAT1 standard can be inflated to an arbitrary extent by any holder of any amount of the token. The total amount of the token can be increased as high as the malicious actor pleases. This is true for every CAT1 on the Chia blockchain regardless of issuance rules. This attack is auditable on chain, so maliciously altered coins can potentially be marked by off-chain observers as malicious.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"chia-blockchain tokens can be inflated to an arbitrary extent","id":"CVE-2022-36447","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2022-36448"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.4.4rc3"],"package":"chia-blockchain","purl":null,"source":"GHSA-pvjg-jwp3-mrj5"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.4.4rc3"],"package":"chia-blockchain","purl":"pkg:pypi/chia-blockchain","source":"GHSA-pvjg-jwp3-mrj5"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.4.4rc3"],"package":"chia-blockchain","purl":"pkg:pypi/chia-blockchain","source":"PYSEC-2022-43072"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-36446"},"products":["n/a"],"published":"2022-07-29","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":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"Any holder of a Chia CAT1 token can arbitrarily inflate the total supply, compromising the token's economic integrity and requiring off-chain mitigation.","url":"https://insights.sbomify.com/CVE-2022-36447/"}