Vulnerability in github.com/crypto-org-chain/cronos (CVE-2021-43839)
Summary
Vulnerability in github.com/crypto-org-chain/cronos (CVE-2021-43839). Data can be tampered with by attackers. Mitigation: upgrade to 0.6.5 or later.
Original description
The description as published by the source.
Impact
In Cronos nodes running versions before v0.6.5, it is possible to take transaction fees from Cosmos SDK's FeeCollector for the current block by sending a custom crafted MsgEthereumTx.
User funds and balances are safe.
Patches
This problem has been patched in Cronos v0.6.5 on the mempool level.
The next network upgrade with consensus-breaking changes will patch it on the consensus level.
Workarounds
There are no tested workarounds. All validator node operators are recommended to upgrade to Cronos v0.6.5 at their earliest possible convenience.
Credits
Thank you to @zb3 for reporting this issue on Cronos Immunefi Bug Bounty Program, to @cyril-crypto for reproducing the issue and to @yihuang and @thomas-nguy for patching the issue on the CheckTx (mempool) and the DeliverTx (consensus) levels.
For more information
If you have any questions or comments about this advisory:
- Open a discussion in crypto-org-chain/cronos
- Email us at chain@crypto.org
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-43839 has been found in github.com/crypto-org-chain/cronos.
Data can be tampered with by attackers.
What to do: upgrade github.com/crypto-org-chain/cronos to 0.6.5 or later.
If unsure, ask your IT team or search "github.com/crypto-org-chain/cronos CVE-2021-43839" on the vendor's site.
CVE-2021-43839 (github.com/crypto-org-chain/cronos) — CWE-670
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.6.5 — apply immediately
Workaround: There are no tested workarounds.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-670) exists in github.com/crypto-org-chain/cronos.
Check the vendor advisory for the affected versions of github.com/crypto-org-chain/cronos.
Severity: ?. Data can be tampered with by attackers.
Update to 0.6.5.
Workaround: There are no tested workarounds.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/crypto-org-chain/cronos' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/crypto-org-chain/cronos' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/crypto-org-chain/cronosを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There are no tested workarounds.パッチが適用されるまでの応急処置として、There are no tested workarounds. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/crypto-org-chain/cronos to 0.6.5ステージング環境で 0.6.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com