CVE-2022-36447
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Chia Network CAT1 Standard 1.0.0 contains a vulnerability that allows any holder of CAT1 tokens to arbitrarily inflate the total supply. By exploiting the minting mechanism, a malicious actor can create additional tokens beyond the original issuance, affecting every CAT1 token on the Chia blockchain regardless of its issuance rules.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify CAT1 Standard version in useReview your deployed token contracts or token issuance records to determine if CAT1 Standard version 1.0.0 is active in your environment. Check any token launcher IDs or references in your applications that interact with Chia tokens.Affected if CAT1 Standard version 1.0.0 is deployed or referenced in your environment
-
Scan wallets for CAT1 tokensInspect all wallets, addresses, or accounts in your environment for any CAT1 token holdings. Use Chia blockchain explorers or CLI tools to list all CAT1 token balances associated with your addresses.Affected if Any CAT1 tokens are present in your wallets or addresses
-
Verify token supply integrityQuery the on-chain total supply for any CAT1 tokens you hold or manage. Compare the current supply against the original issuance amount or known legitimate supply figures. Look for unexpected increases in token quantity.Affected if The current total supply of any CAT1 token exceeds the original issuance or expected supply
-
Check for unauthorized minting activityReview transaction history for any minting operations (XCH minting or additional issuance) associated with CAT1 token launcher IDs in your environment. Look for transactions with puzzle hashes related to the CAT1 minting mechanism.Affected if Minting transactions exist that were not initiated by authorized token issuers
You are affected if your environment uses CAT1 Standard 1.0.0 and holds any CAT1 tokens, or if any CAT1 tokens show supply discrepancies from their original issuance.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataMigrate all CAT1 tokens to a patched token standard (such as CAT2) and update all integrated applications, wallets, and services to use the new standard. Off-chain observers should flag tokens with suspicious supply increases.
- Consultation25.0 h
- Implementation50.0 h
- Testing25.0 h
- Review / QA20.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $34,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36447 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36447 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data