# CVE-2019-3921: Memory corruption in Alcatel Lucent I-240W-Q GPON ONT

> A remote authenticated attacker can execute arbitrary code on Alcatel Lucent I-240W-Q GPON ONT devices via a stack buffer overflow in the USB form handler.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-c4vw-m533-crpc

## What is CVE-2019-3921?

CVE-2019-3921 is a high-severity memory corruption vulnerability in Tenable Alcatel Lucent I-240W-Q GPON ONT, published on 5 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Alcatel Lucent I-240W-Q GPON ONT using firmware version 3FE54567BOZJ19 is vulnerable to a stack buffer overflow via crafted HTTP POST request sent by a remote, authenticated attacker to /GponForm/usb_Form?script/. An attacker can leverage this vulnerability to potentially execute arbitrary code.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2019-3921?

It affects 1 product.


Products: Nokia I-240w-Q Gpon Ont Firmware.

## How do I fix CVE-2019-3921?

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

## Is CVE-2019-3921 being exploited?

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

Public exploit code:

- Alcatel-Lucent (Nokia) GPON I-240W-Q - Buffer Overflow (exploitdb)

## Other vulnerabilities in Tenable Alcatel Lucent I-240W-Q GPON ONT

- [CVE-2019-3918](https://insights.sbomify.com/CVE-2019-3918/): Hardcoded credentials in Alcatel Lucent I-240W-Q GPON ONT (critical 9.8)
- [CVE-2019-3922](https://insights.sbomify.com/CVE-2019-3922/): Memory corruption in Alcatel Lucent I-240W-Q GPON ONT (critical 9.8)
- [CVE-2019-3919](https://insights.sbomify.com/CVE-2019-3919/): Command injection in Alcatel Lucent I-240W-Q GPON ONT (high 8.8)
- [CVE-2019-3920](https://insights.sbomify.com/CVE-2019-3920/): Command injection in Alcatel Lucent I-240W-Q GPON ONT (high 8.8)
- [CVE-2019-3917](https://insights.sbomify.com/CVE-2019-3917/): Missing authorization in Alcatel Lucent I-240W-Q GPON ONT (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3921 and fix it if it is affected.

What it is: CVE-2019-3921 is a high-severity memory corruption vulnerability in Tenable Alcatel Lucent I-240W-Q GPON ONT, published on 5 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-3921 in the wild and no public exploit code.

Affected product: Tenable Alcatel Lucent I-240W-Q GPON ONT. 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-2019-3921/ (Markdown: https://insights.sbomify.com/CVE-2019-3921/index.md)
```

## Sources

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

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