# CVE-2024-36671: Integer overflow in n/a

> An integer overflow in NodeMCU's struct module allows attackers to cause denial of service or potentially execute code.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2024
- **Updated:** 4 Dec 2024
- **Also known as:** GHSA-g724-p2vc-8mfg

## What is CVE-2024-36671?

CVE-2024-36671 is a critical vulnerability in n/a, published on 29 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

nodemcu before v3.0.0-release_20240225 was discovered to contain an integer overflow via the getnum function at /modules/struct.c.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2024-36671?


## How do I fix CVE-2024-36671?

No fix has been published for CVE-2024-36671 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-36671 being exploited?

There is no known exploitation of CVE-2024-36671 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36671 and fix it if it is affected.

What it is: CVE-2024-36671 is a critical vulnerability in n/a, published on 29 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36671 in the wild and no public exploit code.

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-2024-36671/ (Markdown: https://insights.sbomify.com/CVE-2024-36671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-36671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-36671
- OSV: https://osv.dev/vulnerability/CVE-2024-36671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-36671/
Summaries are generated and may contain mistakes; the official description above is the record.