# CVE-2019-11885: Information disclosure in n/a

> Attackers can recover cleartext passwords from eyeDisk devices by sniffing USB traffic or sending specific SCSI commands, bypassing authentication.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xhx6-jqvp-55rr

## What is CVE-2019-11885?

CVE-2019-11885 is a medium-severity vulnerability in n/a, published on 12 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

eyeDisk implements the unlock feature by sending a cleartext password. The password can be discovered by sniffing USB traffic or by sending a 06 05 52 41 01 b0 00 00 00 00 00 00 SCSI command.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2019-11885?

It affects 1 product.


Products: Eye-Disk Eyedisk.

## How do I fix CVE-2019-11885?

No fix has been published for CVE-2019-11885 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-11885 being exploited?

There is no known exploitation of CVE-2019-11885 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11885 and fix it if it is affected.

What it is: CVE-2019-11885 is a medium-severity vulnerability in n/a, published on 12 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11885 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-11885/ (Markdown: https://insights.sbomify.com/CVE-2019-11885/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11885
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11885
- OSV: https://osv.dev/vulnerability/CVE-2019-11885

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-11885/
Summaries are generated and may contain mistakes; the official description above is the record.