CVE-2018-11720
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 · uneditedXovis PC2, PC2R, and PC3 devices through 3.6.0 allow Directory Traversal.
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 confidenceDirectory traversal vulnerability in Xovis PC2, PC2R, and PC3 device firmware versions 3.6.0 and earlier allows remote attackers to access arbitrary files on the filesystem via specially crafted path traversal sequences in HTTP requests.
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<= 3.6.0<= 3.6.0<= 3.6.0CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Xovis devices on your networkScan your network for devices with Xovis PC2, PC2R, or PC3 hostnames, or identify them by MAC vendor prefix if known. Check your network inventory or perform an ARP/Nmap scan to locate these devices.Affected if Any Xovis PC2, PC2R, or PC3 devices are present on the network
-
Check device firmware versionAccess the device web interface via HTTP and navigate to the system settings or firmware information page. Alternatively, check the device status page or administration panel for the installed firmware version.Affected if Firmware version is 3.6.0 or lower
-
Verify HTTP web interface is accessibleAttempt to reach the device HTTP interface by entering the device IP address in a web browser. Confirm the interface loads and accepts requests.Affected if The web interface is exposed and reachable on the network
-
Inspect HTTP access logs for path traversal patternsIf available, review the device HTTP access logs or WAF/IDS logs for requests containing ../ sequences, such as /..// or /..\/..\/ , which indicate exploitation attempts.Affected if Path traversal patterns are present in logs, indicating potential exploitation
You are affected if you have Xovis PC2, PC2R, or PC3 devices running firmware version 3.6.0 or earlier with their HTTP web interface accessible on your network.
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 dataUpgrade device firmware to a version beyond 3.6.0 if available; otherwise implement network segmentation, restrict web interface access to trusted networks, and deploy WAF rules to detect and block path traversal patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11720 — 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-11720 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