CVE-2019-10950
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 · uneditedFujifilm FCR Capsula X/ Carbon X/ FCR XC-2, model versions CR-IR 357 FCR Carbon X, CR-IR 357 FCR XC-2, FCR-IR 357 FCR Capsula X provide insecure telnet services that lack authentication requirements. An attacker who successfully exploits this vulnerability may be able to access the underlying operating 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 · high confidenceFujifilm FCR medical imaging devices (Capsula X, Carbon X, XC-2) expose telnet services without any authentication. This allows any network attacker to connect directly to the device and execute commands on the underlying operating system, potentially compromising patient data and device functionality.
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 dataall versionsall versionsall versionsCVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 device modelLocate the device label or check network inventory for Fujifilm FCR models: Cr Ir 357 Fcr Carbon X, Cr Ir 357 Fcr Xc 2, or Cr Ir 357 Fcr Capsula X. This information is typically on a physical label on the device or in the device's system information menu.Affected if The device matches any of these three model names.
-
Scan for open telnet portUse a network port scanner (such as nmap) to check if TCP port 23 is open and accessible on the device IP address. Example: nmap -p 23 -Pn <device_ip>Affected if Port 23/telnet is open and reachable on the network.
-
Verify telnet requires no authenticationAttempt to connect to the device via telnet without providing any credentials. Use: telnet <device_ip> . Observe whether you are immediately dropped to a shell prompt or command line without being prompted for username or password.Affected if Connection succeeds and provides shell access without any authentication prompt.
-
Check network exposure of telnet serviceReview firewall rules or network segmentation to determine whether the telnet port is accessible from untrusted network segments (guest networks, internet-facing interfaces, or untrusted VLANs).Affected if Telnet port 23 is accessible from any network segment outside of a dedicated management VLAN.
You are affected if you operate any Fujifilm Cr Ir 357 Fcr Carbon X, Fcr Xc 2, or Fcr Capsula X device and telnet port 23 is open and accessible without authentication 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 dataDisable the unauthenticated telnet service on affected devices; if telnet is required for legacy reasons, implement network segmentation and firewall rules to restrict access to authorized personnel only, and contact Fujifilm for firmware updates.
- Consultation8.0 h
- Implementation4.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10950 — 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-10950 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