GHSA-p228-4mrh-ww7r

Suggest an improvement
Source
https://github.com/advisories/GHSA-p228-4mrh-ww7r
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/12/GHSA-p228-4mrh-ww7r/GHSA-p228-4mrh-ww7r.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-p228-4mrh-ww7r
Aliases
Related
Published
2022-12-30T16:57:11Z
Modified
2024-08-21T16:28:47.143282Z
Severity
  • 7.2 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L CVSS Calculator
Summary
Elrond-GO processing: fallback search of SCRs when not found in the main cache
Details

Impact

Processing issue, 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.

Patches

All versions >= v1.3.50 will contain this patch

Workarounds

For the moment there is no workaround

References

N/A

For more information

If you have any questions or comments about this advisory: * Open an issue in elrond-go main repo

Database specific
{
    "nvd_published_at": "2022-12-28T07:15:00Z",
    "github_reviewed_at": "2022-12-30T16:57:11Z",
    "severity": "HIGH",
    "github_reviewed": true,
    "cwe_ids": [
        "CWE-669"
    ]
}
References

Affected packages

Go / github.com/ElrondNetwork/elrond-go

Package

Name
github.com/ElrondNetwork/elrond-go
View open source insights on deps.dev
Purl
pkg:golang/github.com/ElrondNetwork/elrond-go

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.3.50

Database specific

{
    "last_known_affected_version_range": "<= 1.3.48"
}