Gpon FirmwareOperating system · Hinet

CVE-2019-15065

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
A service which is hosted on port 6998 in HiNet GPON firmware < I040GWR190731 allows an attacker to execute a specific command to read arbitrary files. CVSS 3.0 Base score 9.3. CVSS vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L).

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 confidence

HiNet GPON fiber optic router firmware versions before I040GWR190731 contain a service listening on port 6998 that suffers from an arbitrary file read vulnerability. An unauthenticated attacker can send a specific command to the service to read any file on the system, likely due to insufficient input validation or path traversal in the file request handler.

MitigationUpdate HiNet GPON firmware to version I040GWR190731 or later. If immediate patching is not possible, restrict network access to port 6998 using firewall rules or disable the service if not required.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 device model and confirm it is a HiNet GPON router
    Check the device label, administrative web interface, or SNMP information to confirm the device is an HiNet GPON fiber optic router model (such as I040GWR series)
    Affected if The device is not an HiNet GPON router - the vulnerability only affects this specific product line
  2. Check the installed firmware version
    Access the router administrative interface or use the command line (telnet/ssh if available) to retrieve the firmware version. Compare it against the affected version i040gwr190731
    Affected if The firmware version is less than i040gwr190731 (for example, i040gwr190615 or earlier)
  3. Verify if port 6998 is open and listening
    Perform a port scan against the router from the LAN or WAN interface using 'nmap -p 6998 <router_ip>' or similar network scanning tool
    Affected if Port 6998 is open and responding - this indicates the vulnerable service is running
  4. Test for unauthorized file access (controlled check)
    Send a crafted request to port 6998 attempting to read a non-sensitive file (such as /etc/passwd or a known configuration file). Note: This is an active test and should only be performed on systems you own or have explicit permission to test
    Affected if The service returns file contents from arbitrary paths, confirming the path traversal vulnerability is present

The device is affected if it is a HiNet GPON router running firmware version earlier than i040gwr190731 with port 6998 open and accessible, and the service allows reading arbitrary files without authentication.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update HiNet GPON firmware to version I040GWR190731 or later. If immediate patching is not possible, restrict network access to port 6998 using firewall rules or disable the service if not required.

Fix this in Gpon Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15065 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-15065 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