GHSA-75qh-gg76-p2w4 GO-2024-3101 RUSTSEC-2024-0366
CWA-2023-004: Excessive number of function parameters in compiled Wasm
Medium
Gocrates.io
- Severity
- 0.0 / 10
- Medium · CVSS 4.0
- Exploit chance (EPSS)
- —
- No score published
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
- Available
- 2 packages have a fixed version
Description
A specifically crafted Wasm file can cause the VM to consume excessive amounts of memory when compiling a contract. This can lead to high memory usage, slowdowns, potentially a crash and can poison a lock in the VM, preventing any further interaction with contracts.
For more information, see CWA-2023-004.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/CosmWasm/wasmvm | < 1.2.5 |
1.2.5 |
| github.com/CosmWasm/wasmvm | >= 1.3.0, < 1.3.1 |
1.3.1 |
| github.com/CosmWasm/wasmvm | >= 1.4.0, < 1.4.2 |
1.4.2 |
| github.com/CosmWasm/wasmvm | >= 1.5.0, < 1.5.1 |
1.5.1 |
| github.com/CosmWasm/wasmvm | < 1.2.5>= 1.3.0, < 1.3.1>= 1.4.0, < 1.4.2>= 1.5.0, < 1.5.1 |
1.2.51.3.11.4.21.5.1 |
crates.io
| Package | Vulnerable | Fixed in |
|---|---|---|
| cosmwasm-vm | < 1.2.8 |
1.2.8 |
| cosmwasm-vm | >= 1.3.0, < 1.3.4 |
1.3.4 |
| cosmwasm-vm | >= 1.4.0, < 1.4.2 |
1.4.2 |
| cosmwasm-vm | >= 1.5.0, < 1.5.1 |
1.5.1 |
| cosmwasm-vm | >= 0.0.0-0, < 1.2.8>= 1.3.0, < 1.3.4>= 1.4.0, < 1.4.2>= 1.5.0, < 1.5.1 |
1.2.81.3.41.4.21.5.1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
github.com/CosmWasm/wasmvm Go → 1.2.5
- go
go get github.com/CosmWasm/wasmvm@v1.2.5 && go mod tidy
cosmwasm-vm crates.io → 1.2.8
- cargo
cargo update -p cosmwasm-vm --precise 1.2.8
Severity breakdown
CVSS 4.0 0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
- Attack vector
- Network
- Attack complexity
- Low
- Attack requirements
- None
- Privileges required
- None
- User interaction
- None
- Confidentiality (vulnerable system)
- None
- Integrity (vulnerable system)
- None
- Availability (vulnerable system)
- Low
- Confidentiality (subsequent systems)
- None
- Integrity (subsequent systems)
- None
- Availability (subsequent systems)
- None
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-mx2j-7cmv-353c wasmvm: Malicious smart contract can slow down block production | Medium | Also affects cosmwasm-vm |
| GHSA-2q97-m5rc-p3gp CosmWasm VM Incorrect metering | Medium | Also affects cosmwasm-vm |
| GHSA-vmqh-5232-v43r Panic in wasmvm can slow down block production | Medium | Also affects cosmwasm-vm |
| GHSA-rg2q-2jh9-447q Gas mispricing in cosmwasm-vm | Medium | Also affects cosmwasm-vm |
| GHSA-cggf-277g-3q54 pypdf has possible large memory usage when parsing page tree | High | Same weakness, CWE-400 |
| GHSA-3g3m-2fjr-6pw4 Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal | Medium | Same weakness, CWE-400 |
| GHSA-42gh-23hr-vphw pypdf has possible long runtimes when retrieving page labels | High | Same weakness, CWE-400 |
| GHSA-4vqv-7265-gm2w pypdf has possible large memory usage for exceptions in strict mode | High | Same weakness, CWE-400 |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor