CVE-2019-6178
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 information leakage vulnerability in Iomega and LenovoEMC NAS products could allow disclosure of some device details such as Share names through the device API when Personal Cloud is enabled. This does not allow read, write, delete, or any other access to the underlying file systems and their contents.
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 confidenceAn information disclosure vulnerability in Iomega and LenovoEMC NAS devices exposes Share names through the device API when Personal Cloud is enabled. This allows attackers to enumerate shared folder names via unauthenticated API requests, but provides no access to actual file contents or file system operations.
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.0.24.34808= 4.0.24.34808= 3.2.16.30221= 3.2.16.30221= 2.1.50.30227= 3.2.16.30221= 2.1.50.30227= 2.1.50.30227CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 the NAS device model and firmware versionAccess the device admin interface or check the device settings to find the exact model number and installed firmware versionAffected if The device is a Lenovo Px12 350r, Lenovo Ix12 300r, Lenovo Home Media Network Hard Drive, Lenovo Storecenter Ix2 200, Lenovo Storecenter Ix4 200d, or Lenovo Storecenter Ix4 200rl AND the firmware version matches 4.0.24.34808, 3.2.16.30221, or 2.1.50.30227 exactly
-
Verify Personal Cloud statusNavigate to the device settings and check whether Personal Cloud functionality is enabledAffected if Personal Cloud is currently turned on in the device configuration
-
Confirm API endpoint accessibilityAttempt to access the device API endpoints externally or internally without providing authentication credentials to see if share names are returnedAffected if Unauthenticated API requests successfully return share or folder names from the device
You are affected if your device is one of the listed models with a matching firmware version AND Personal Cloud is enabled, allowing unauthenticated enumeration of share names.
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 dataIf Personal Cloud functionality is not required, disable it in the device settings. Otherwise, apply vendor firmware updates when available and restrict network access to the management interface.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6178 — 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-6178 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