CVE-2020-17385
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 · uneditedCellopoint CelloOS v4.1.10 Build 20190922 does not validate URL inputted properly, which allows unauthorized user to launch Path Traversal attack and access arbitrate file on the system.
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 confidenceCellopoint CelloOS v4.1.10 Build 20190922 fails to validate URL input properly, enabling path traversal attacks where attackers can use sequences like '../' to access files outside the web root directory. This allows unauthorized read access to arbitrary files on the system.
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= 4.1.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Cellopoint CelloOS is installedCheck for the Cellopoint application on the system - look for installation directories, running services, or the web interface on common ports (typically 80/443). Use commands like 'ps aux | grep cello' or check known installation paths.Affected if Cellopoint CelloOS software is found running on the system
-
Confirm the installed version is 4.1.10Access the web administration interface or check version files. Look for version information in the web UI (often in About/Help sections), or check system files like /opt/cellopoint/version or similar installation manifests. Compare against the affected version: 4.1.10 Build 20190922.Affected if The installed version is exactly 4.1.10 (or Build 20190922)
-
Verify the web server component is accessibleAttempt to access the CelloOS web interface via HTTP/HTTPS. This vulnerability exploits URL parameters, so confirm the web service is running and accepting requests.Affected if The CelloOS web interface is accessible and responds to requests
-
Test for path traversal vulnerabilitySend a crafted HTTP request with directory traversal sequences to accessible URL endpoints. For example, request a URL like '/../../../../etc/passwd' or similar paths outside the web root. Observe if the server returns file contents or exposes path traversal.Affected if The server returns content from files outside the web root directory when using '../' sequences in URLs
You are affected if Cellopoint CelloOS version 4.1.10 is installed and the web interface is accessible, allowing unauthorized file access via directory traversal in URL parameters.
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 dataImplement strict input validation for all URL parameters, whitelist allowed characters, normalize paths, and verify that resolved paths remain within expected directories. Consider using built-in path resolution functions that prevent directory traversal.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-17385 — 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-2020-17385 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