CVE-2019-13411
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 “invalid command” handler issue was discovered in HiNet GPON firmware < I040GWR190731. It allows an attacker to execute arbitrary command through port 3097. CVSS 3.0 Base score 10.0. CVSS vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).
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 confidenceA command injection vulnerability in the 'invalid command' handler of HiNet GPON firmware versions prior to I040GWR190731 allows unauthenticated remote attackers to execute arbitrary operating system commands by sending specially crafted packets to port 3097. The lack of input sanitization in the handler enables complete system compromise.
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< i040gwr190731CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify HiNet GPON device modelCheck the device label, web interface, or SNMP for the model number. Common GPON ONT models from HiNet include HGxxxx series. Access the device admin panel via HTTP/HTTPS or check physical labeling.Affected if The device is a HiNet GPON Optical Network Terminal (ONT)
-
Check firmware versionLog into the device web interface (typically 192.168.1.1 or similar) and navigate to Status or System Info page to view the firmware version. Alternatively, check via SNMP OID or console access if available.Affected if The firmware version is older than i040gwr190731 (for example, i040gwr1901xx, i040gwr18xxxx, or any version string that alphabetically precedes i040gwr190731)
-
Verify port 3097 is listeningFrom a network-connected host, run 'nmap -p 3097 <target-ip>' or 'nc -zv <target-ip> 3097' to check if the GPON device has port 3097 open and listening.Affected if Port 3097 returns as open on the GPON device
-
Check network exposure of port 3097Perform an external port scan from outside the LAN or review firewall logs to determine if port 3097 is accessible from untrusted networks (WAN/Internet). Check router/firewall rules for any port forwarding or DMZ configurations exposing port 3097.Affected if Port 3097 is reachable from the WAN or untrusted network segments
A user is affected if they operate a HiNet GPON device with firmware version prior to i040gwr190731 that has port 3097 exposed to network attackers.
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.
dbcve · scopedUpgrade HiNet GPON firmware to version I040GWR190731 or later. If immediate patching is not feasible, restrict network access to port 3097 through firewall rules or network segmentation to prevent external exploitation.
i040gwr190731 or later
- 1. Identify the current GPON firmware version on the device
- 2. Download firmware version i040gwr190731 or later from the official HiNet vendor source
- 3. Access the device web management interface or CLI
- 4. Navigate to the firmware upgrade section
- 5. Upload the fixed firmware file (i040gwr190731 or newer)
- 6. Allow the device to complete the firmware update process
- 7. Reboot the device as prompted
- 8. Verify the new firmware version is installed and port 3097 is no longer exposing the vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13411 — 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-2019-13411 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