dbcve.org
Gpon FirmwareOperating system · Hinet

CVE-2019-15064

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
HiNet GPON firmware version < I040GWR190731 allows an attacker login to device without any 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 · moderate confidence

HiNet GPON router firmware versions prior to I040GWR190731 contain an authentication bypass vulnerability that allows unauthenticated attackers to gain full administrative access to the device by directly accessing the login functionality without credentials.

MitigationUpgrade HiNet GPON firmware to version I040GWR190731 or later to remediate this vulnerability. If immediate patching is not possible, restrict physical and network access to the device's management interface to limit exposure.

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
Gpon FirmwareOperating system
Affected:< i040gwr190731

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.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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the HiNet GPON router firmware version
    Access the device's web management interface and navigate to the status or system information page, or use the command line interface (telnet/ssh) to run 'show version' or similar command to retrieve the firmware build number
    Affected if The displayed firmware version is earlier than I040GWR190731 (for example, I040GWR190501 or any version number that comes before 190731)
  2. Confirm the device model is HiNet GPON
    Check the device label or the management interface for the exact model number (such as I040GWR or similar GPON router models from HiNet)
    Affected if The device is a HiNet GPON router and the firmware version shown is before I040GWR190731
  3. Verify if the web management interface is accessible
    Attempt to access the device's IP address via HTTP/HTTPS from an internal network location to confirm the web interface is running
    Affected if The web interface is reachable and the firmware version is below I040GWR190731
  4. Check for unauthenticated access to login function
    From a browser, navigate directly to the login page URL (typically /login.asp, /index.asp, or /ponauth.html on the device's IP) without providing any credentials, then attempt to access administrative functions
    Affected if You can reach the administrative interface or execute privileged commands without providing valid credentials, indicating the authentication bypass is present

The device is affected if it is a HiNet GPON router running firmware version earlier than I040GWR190731 and the web management interface is accessible, allowing unauthenticated access to administrative functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HiNet GPON firmware to version I040GWR190731 or later to remediate this vulnerability. If immediate patching is not possible, restrict physical and network access to the device's management interface to limit exposure.

Recommended fix High confidence

i040gwr190731 or later

  1. Contact the device vendor or HiNet ISP to obtain the fixed firmware version (i040gwr190731 or later)
  2. Download the firmware update from an official/vendor source only
  3. Access the device management interface using existing credentials (if still functional) or contact vendor for access method
  4. Follow the vendor's documented firmware upgrade procedure, typically via web UI or TFTP
  5. After upgrade, verify the device is accessible and authentication is now required for login
  6. Confirm the new firmware version matches i040gwr190731 or later using the web UI or CLI
Caveat Firmware upgrades on ISP-provided devices may require vendor/ISP coordination and could void warranty if done improperly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gpon Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15064 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-15064 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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