github.com/crypto-org-chain/cronos vulnerabilities

Registry
Go
Latest
1.8.2

5 known advisories

The latest version, 1.8.2, is not affected by any of them. Projects on older versions may be.

Update to the latest version:go get github.com/crypto-org-chain/cronos@v1.8.2

Is your project on an affected github.com/crypto-org-chain/cronos?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for github.com/crypto-org-chain/cronos

  • LowGO-2022-082921 Aug 2024

    Cronos vulnerable to DoS through unintended Contract Selfdestruct in github.com/crypto-org-chain/cronos

    Affected
    <0.8.0
    Fixed in
    0.8.0
  • LowCVE-2022-35936GO-2022-076021 Aug 2024

    Ethermint vulnerable to DoS through unintended Contract Selfdestruct in github.com/crypto-org-chain/cronos

    Affected
    <0.7.1-rc2
    Fixed in
    0.7.1-rc2
  • HighCVE-2022-35936GHSA-f92v-grc2-w2fg18 Aug 2022

    Ethermint vulnerable to DoS through unintended Contract Selfdestruct

    Affected
    <0.7.1-rc2
    Fixed in
    0.7.1-rc2
  • HighGHSA-gwj5-wp6r-5q9f11 Aug 2022

    Cronos vulnerable to DoS through unintended Contract Selfdestruct

    Affected
    <0.8.0
    Fixed in
    0.8.0
  • HighCVE-2021-43839GHSA-f854-hpxv-cw9r6 Jan 2022

    Drainage of FeeCollector's Block Transaction Fees in cronos

    Affected
    <0.6.5
    Fixed in
    0.6.5

Is your github.com/crypto-org-chain/cronos version vulnerable?

Which of your client projects still run an old github.com/crypto-org-chain/cronos?

NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Go packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.