CVE-2024-4641
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOnCell G3470A-LTE Series firmware versions v1.7.7 and prior have been identified as vulnerable due to accepting a format string from an external source as an argument. An attacker could modify an externally controlled format string to cause a memory leak and denial of service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe OnCell G3470A-LTE Series cellular router firmware versions v1.7.7 and prior contains a format string vulnerability where the device accepts format strings from external input without sanitization. An attacker can supply specially crafted format string specifiers (e.g., %x, %s) to leak memory contents from the stack and cause denial of service by crashing the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.7.7<= 1.7.7<= 1.7.7<= 1.7.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device web interface or CLI and locate the product model information. Look for 'OnCell G3470A-LTE' or similar designation in the status or system information page.Affected if The device is a Moxa OnCell G3470A-LTE Series variant (US, EU, US-T, or EU-T)
-
Determine the installed firmware versionIn the device web interface, navigate to the System or Status section to view the firmware version. Alternatively, use the CLI command 'show system info' or 'version' to retrieve the firmware build.Affected if The firmware version is 1.7.7 or earlier (for example, 1.7.6, 1.7.5, 1.5.2, etc.)
-
Check if web management interface is enabledIn the web UI, go to Network or System settings and verify whether the HTTP/HTTPS management interface is enabled. Check if it is bound to WAN or external-facing interfaces.Affected if Web management is enabled and accessible from external networks (WAN interface)
-
Identify services accepting external inputReview the device configuration for services that accept user-supplied strings or parameters. Common candidates include DNS settings, PPP configuration, SNMP community strings, or custom scripts.Affected if Any service or configuration field accepts external (user-provided) input without evident input validation
The device is affected if it is an OnCell G3470A-LTE Series model running firmware version 1.7.7 or earlier AND the web management or other external input-accepting services are enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate firmware to v1.8.0 or later which contains the vendor patch, or implement input validation to ensure external inputs are never used directly as format string arguments in printf-style functions.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4641 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4641 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data