CVE-2017-7915
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 · uneditedAn Improper Restriction of Excessive Authentication Attempts issue was discovered in Moxa OnCell G3110-HSPA Version 1.3 build 15082117 and previous versions, OnCell G3110-HSDPA Version 1.2 Build 09123015 and previous versions, OnCell G3150-HSDPA Version 1.4 Build 11051315 and previous versions, OnCell 5104-HSDPA, OnCell 5104-HSPA, and OnCell 5004-HSPA. An attacker can freely use brute force to determine parameters needed to bypass authentication.
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 · high confidenceThis vulnerability in Moxa OnCell cellular gateway devices (multiple models including G3110-HSPA, G3150-HSDPA, and 5004/5104-HSPA series) allows attackers to perform unlimited brute-force attacks to determine authentication bypass parameters due to the lack of proper rate limiting, account lockout, or CAPTCHA mechanisms.
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.3<= 1.2<= 1.4<= -<= -<= -CVSS 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.0/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 OnCell device modelCheck the product label on the device or log into the web management interface to view the model number under System > Device Information or similarAffected if The device is a G3110-HSPA, G3110-HSDPA, G3150-HSDPA, 5104-HSDPA, 5104-HSPA, or 5004-HSPA model
-
Check the installed firmware versionLog into the web interface and navigate to System > Firmware Version or use the Moxa firmware upgrade tool to query the current firmware versionAffected if Firmware version is 1.3 or lower for G3110-HSPA, 1.2 or lower for G3110-HSDPA, 1.4 or lower for G3150-HSDPA, or any version for 5004/5104 series (version unknown)
-
Verify if authentication rate limiting is enabledIn the web interface, navigate to Security > Authentication or System > Login Settings and look for settings related to login attempt rate limiting or throttlingAffected if No rate limiting option exists or it is disabled, allowing unlimited login attempts
-
Verify if account lockout policy is configuredIn the web interface under Security > Account or Security > Authentication settings, check for account lockout after failed attempts or account lockdown featuresAffected if No account lockout policy is present or configurable, allowing unlimited password guessing
-
Check for CAPTCHA or similar protection on loginOn the device login page (HTTP/HTTPS web interface), attempt multiple failed logins and observe whether any CAPTCHA, image verification, or similar challenge appearsAffected if No CAPTCHA or human verification challenge appears after failed login attempts
The device is affected if it is a vulnerable OnCell model running an affected firmware version AND lacks rate limiting, account lockout, or CAPTCHA protection for authentication attempts.
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 dataImplement account lockout policies, authentication rate limiting, or CAPTCHA after failed login attempts to prevent brute-force attacks; if unavailable via device configuration, contact Moxa for firmware update or implement network-level controls to restrict authentication attempts.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7915 — 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-2017-7915 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