CVE-2023-30300 An issue in the component hang.wasm of WebAssembly 1.0 causes an infinite loop.
Medium 5.5
Published
Updated
Check this codebase for CVE-2023-30300 and fix it if it is affected.
What it is: CVE-2023-30300 is a medium-severity vulnerability in n/a, published on 3 May 2023.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30300 exists.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2023-30300/ (Markdown: https://insights.sbomify.com/CVE-2023-30300/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2023-30300?
CVE-2023-30300 is a medium-severity vulnerability in n/a, published on 3 May 2023.
Official description
An issue in the component hang.wasm of WebAssembly 1.0 causes an infinite loop.
Weakness: CWE-835
Which versions are affected by CVE-2023-30300?
It affects 1 product.
Products include W3 Webassembly.
How do I fix CVE-2023-30300?
Upgrade to a fixed version.
Is CVE-2023-30300 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30300 exists.
Sources
Also known as DEBIAN-CVE-2023-30300, GHSA-pm5m-2p5c-6mv8, UBUNTU-CVE-2023-30300.