Ceph StorageApplication · Redhat
CVE-2020-1699
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 path traversal flaw was found in the Ceph dashboard implemented in upstream versions v14.2.5, v14.2.6, v15.0.0 of Ceph storage and has been fixed in versions 14.2.7 and 15.1.0. An unauthenticated attacker could use this flaw to cause information disclosure on the host machine running the Ceph dashboard.
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 path traversal vulnerability in the Ceph dashboard allows unauthenticated attackers to access files outside the intended web root directory, potentially exposing sensitive host system files.
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
Ceph StorageApplication
= 4.0= 14.2.5= 14.2.6= 15.0.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.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.
-
Verify if Ceph dashboard is enabledRun 'ceph mgr module ls' and check if 'dashboard' appears in the 'enabled_modules' list, or check the manager status with 'ceph status' and look for dashboard module activityAffected if Ceph dashboard module is enabled and accessible
-
Determine installed Ceph versionRun 'ceph version' or 'ceph -v' to obtain the exact Ceph version numberAffected if Version is 4.0 (Red Hat), 14.2.5, 14.2.6, or 15.0.0 (Linux Foundation)
-
Confirm dashboard is network reachableCheck dashboard configuration with 'ceph config get mgr mgr_dashboard_ssl' and review firewall rules or service bindings; verify the dashboard URL is exposed beyond localhostAffected if Dashboard is bound to a network interface accessible to untrusted users
-
Identify dashboard bind addressRun 'ceph config get mgr mgr_dashboard_addr' to see the IP address the dashboard listens on, and check if it accepts connections from untrusted networksAffected if Dashboard binds to 0.0.0.0 or a non-loopback IP address
Environment is affected if Ceph dashboard is enabled, the version matches 4.0, 14.2.5, 14.2.6, or 15.0.0, and the dashboard is accessible from an untrusted network segment.
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 Ceph to version 14.2.7 or 15.1.0 or later. If immediate upgrade is not possible, restrict network access to the dashboard via firewall rules or disable the dashboard if not required.
Fix this in Ceph Storage
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1699 — 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-1699 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