x/vulndb: potential Go vuln in github.com/ElrondNetwork/elrond-go: CVE-2022-46173

[GoVulnBot]

CVE-2022-46173 references github.com/ElrondNetwork/elrond-go, which may be a Go module.

Description: Elrond-GO is a go implementation for the Elrond Network protocol. Versions prior to 1.3.50 are subject to a processing issue where nodes are affected when trying to process a cross-shard relayed transaction with a smart contract deploy transaction data. The problem was a bad correlation between the transaction caches and the processing component. If the above-mentioned transaction was sent with more gas than required, the smart contract result (SCR transaction) that should have returned the leftover gas, would have been wrongly added to a cache that the processing unit did not consider. The node stopped notarizing metachain blocks. The fix was actually to extend the SCR transaction search in all other caches if it wasn't found in the correct (expected) sharded-cache. There are no known workarounds at this time. This issue has been patched in version 1.3.50.

References:

• NIST: https://nvd.nist.gov/vuln/detail/CVE-2022-46173
• JSON: https://github.com/CVEProject/cvelist/tree/74011a2784fd28758c7676aa32ecd29e83b8dfa4/2022/46xxx/CVE-2022-46173.json
• web: https://github.com/ElrondNetwork/elrond-go/security/advisories/GHSA-p228-4mrh-ww7r
• fix: https://github.com/ElrondNetwork/elrond-go/pull/4718
• fix: https://github.com/ElrondNetwork/elrond-go/commit/39d7ddcb08bb34217dab6daef7cd9d287fb8cab3
• Imported by: https://pkg.go.dev/github.com/ElrondNetwork/elrond-go?tab=importedby

Cross references:

• Module github.com/ElrondNetwork/elrond-go appears in issue #970 NOT_IMPORTABLE
• Module github.com/ElrondNetwork/elrond-go appears in issue #971 NOT_IMPORTABLE

See doc/triage.md for instructions on how to triage this report.

modules:
  - module: github.com/ElrondNetwork/elrond-go
    packages:
      - package: elrond-go
description: |
    Elrond-GO is a go implementation for the Elrond Network protocol. Versions prior to 1.3.50 are subject to a processing issue where nodes are affected when trying to process a cross-shard relayed transaction with a smart contract deploy transaction data. The problem was a bad correlation between the transaction caches and the processing component. If the above-mentioned transaction was sent with more gas than required, the smart contract result (SCR transaction) that should have returned the leftover gas, would have been wrongly added to a cache that the processing unit did not consider. The node stopped notarizing metachain blocks. The fix was actually to extend the SCR transaction search in all other caches if it wasn't found in the correct (expected) sharded-cache. There are no known workarounds at this time. This issue has been patched in version 1.3.50.
cves:
  - CVE-2022-46173
references:
  - web: https://github.com/ElrondNetwork/elrond-go/security/advisories/GHSA-p228-4mrh-ww7r
  - fix: https://github.com/ElrondNetwork/elrond-go/pull/4718
  - fix: https://github.com/ElrondNetwork/elrond-go/commit/39d7ddcb08bb34217dab6daef7cd9d287fb8cab3

[gopherbot]

Change https://go.dev/cl/459639 mentions this issue: data/excluded: batch add GO-2022-1200

[gopherbot]

Change https://go.dev/cl/460419 mentions this issue: data/excluded: batch add GO-2022-1253, GO-2022-1251, GO-2022-1250, GO-2022-1248, GO-2022-1245, GO-2022-1243, GO-2022-1240, GO-2022-1239, GO-2022-1236, GO-2022-1235, GO-2022-1225, GO-2022-1220, GO-2022-1219, GO-2022-1218, GO-2022-1216, GO-2022-1208, GO-2022-1206, GO-2022-1204, GO-2022-1200, GO-2022-1192, GO-2022-1190, GO-2022-1189, GO-2022-1258, GO-2022-1226, GO-2022-1214, GO-2022-1210, GO-2022-1212

[gopherbot]

Change https://go.dev/cl/592835 mentions this issue: data/reports: unexclude 50 reports

[gopherbot]

Change https://go.dev/cl/607232 mentions this issue: data/reports: unexclude 20 reports (30)