CVE-2024-4639
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 a lack of neutralized inputs in IPSec configuration. An attacker could modify the intended commands sent to target functions, which could cause malicious users to execute unauthorized commands.
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 wireless gateway contains a command injection vulnerability in its IPSec configuration functionality. Firmware versions v1.7.7 and prior fail to properly neutralize user inputs within the IPSec settings, allowing attackers to modify configuration commands and execute unauthorized system commands.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm device modelAccess the device admin interface or CLI and identify the exact model number. Look for OnCell G3470A-LTE variants (US, EU, US-T, EU-T).Affected if The device is any Moxa OnCell G3470A-LTE Series variant.
-
Check firmware versionNavigate to the device status or system information page in the web admin interface, or use the CLI command to display firmware version. Compare the installed version against v1.7.7.Affected if Firmware version is v1.7.7 or lower.
-
Verify IPSec configuration statusLocate the IPSec settings section in the device web interface under VPN or security configuration, or use the CLI to display IPSec status. Determine if IPSec is enabled or has any configured tunnels.Affected if IPSec is enabled or has active IPSec tunnel configurations.
-
Inspect IPSec settings for anomaliesReview all IPSec-related configuration fields including tunnel names, remote gateway addresses, and authentication parameters. Look for unexpected characters, semicolons, pipes, or command-like syntax in any user-editable fields.Affected if Any IPSec configuration fields contain unexpected command syntax or suspicious input patterns.
If the device is an OnCell G3470A-LTE with firmware v1.7.7 or lower and IPSec is configured or enabled, the environment is affected by this command injection vulnerability.
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 the device firmware to a version newer than v1.7.7 once available from the vendor. Until then, restrict administrative access to trusted networks only and consider disabling IPSec if not actively required.
- Consultation3.0 h
- Implementation2.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4639 — 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-4639 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