Gpon FirmwareOperating system · Hinet

CVE-2019-13412

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 3097 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

A command injection vulnerability in the service on port 3097 of HiNet GPON firmware versions prior to I040GWR190731 allows unauthenticated remote attackers to execute specific commands to read arbitrary files from the device's filesystem. The CVSS vector indicates a network-exploitable flaw with no user interaction or privileges required, achieving high confidentiality impact.

MitigationUpgrade HiNet GPON firmware to version I040GWR190731 or later. If immediate patching is not possible, restrict network access to port 3097 via firewall rules or disable the vulnerable service until the update can be applied.

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 HiNet GPON device
    Access the device's admin interface or check the device model number on the physical device or in its network configuration. Confirm the device is a HiNet GPON optical network terminal or router.
    Affected if The device is not a HiNet GPON product, then this CVE does not apply.
  2. Check firmware version
    Log into the device's web admin panel or access via SSH/Telnet to view system information or firmware version. The version is typically displayed under 'System Status', 'Device Info', or similar menu. Compare the version string to 'i040gwr190731'.
    Affected if The installed firmware version is earlier than i040gwr190731 (for example, i040gwr190101 or older), indicating the device is within the affected version range.
  3. Verify port 3097 is listening
    From a trusted internal host, run a port scan against the device: 'nmap -p 3097 <device_ip>' or use 'netcat -zv <device_ip> 3097'. Alternatively, check on the device itself using 'netstat -tuln | grep 3097' or 'ss -tuln | grep 3097' if you have shell access.
    Affected if Port 3097 is open and accepting connections, meaning the vulnerable service is exposed.
  4. Confirm service accessibility
    If the device is on an internal network, verify whether port 3097 is reachable from network segments where untrusted users could originate traffic. Check firewall rules or ACLs that may permit or block access to this port.
    Affected if Port 3097 is reachable from network segments with untrusted users or directly from the internet, increasing exposure to remote exploitation.

If the device is a HiNet GPON with firmware version earlier than i040gwr190731 and port 3097 is exposed on the network, the environment is affected by this CVE.

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

Upgrade HiNet GPON firmware to version I040GWR190731 or later. If immediate patching is not possible, restrict network access to port 3097 via firewall rules or disable the vulnerable service until the update can be applied.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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