CVE-2018-19031
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 · uneditedA command injection vulnerability exists when the authorized user passes crafted parameter to background process in the router. This affects 360 router series products (360 Safe Router P0,P1,P2,P3,P4), the affected version is V2.0.61.58897.
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 confidenceCommand injection vulnerability in 360 Safe Router series (P0, P1, P2, P3, P4) firmware V2.0.61.58897 allows authenticated users to inject arbitrary commands through crafted parameters passed to a background process, enabling complete system compromise with the privileges of the affected service.
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= 2.0.61.58897= 2.0.61.58897= 2.0.61.58897= 2.0.61.58897= 2.0.61.58897CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 router modelCheck the router label or admin interface for the model number (P0, P1, P2, P3, or P4)Affected if Router is one of the 360 Safe Router series models (P0, P1, P2, P3, P4)
-
Check firmware versionAccess router admin interface (typically at 192.168.1.1 or similar) and navigate to System Settings or Status page to view firmware version, or use CLI command 'cat /proc/version' or 'ver' if availableAffected if Firmware version is exactly 2.0.61.58897
-
Verify admin interface accessibilityCheck if router web admin interface or remote management (WAN access) is exposed to untrusted networks by reviewing router firewall settings and port forwarding rulesAffected if Administrative interface is accessible from untrusted networks (WAN) or without proper network segmentation
-
Review user accountsCheck router admin interface User Management or Accounts section to review who has administrative accessAffected if Multiple user accounts exist or default credentials may be in use, increasing attack surface
-
Monitor for compromise indicatorsInspect running processes via CLI (ps command) or check system logs for unexpected processes, unusual network connections, or commands containing suspicious patterns like semicolons or pipe charactersAffected if Unexpected processes, suspicious command executions in logs, or unfamiliar network connections are observed
User is affected if they own a 360 Safe Router model (P0-P4) running firmware version 2.0.61.58897 with accessible admin interface to potential 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.
From vendor dataApply vendor firmware patch when available; until then, limit router administrative interface access to trusted users only and monitor for suspicious activity.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19031 — 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-2018-19031 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