CVE-2013-7404
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 · uneditedGE Healthcare Discovery NM 750b has a password of 2getin for the insite account for (1) Telnet and (2) FTP, which has unspecified impact and attack vectors. NOTE: it is not clear whether this password is default, hardcoded, or dependent on another system or product that requires a fixed value.
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 confidenceGE Healthcare Discovery NM 750b medical imaging device contains a hardcoded/default password '2getin' for the 'insite' account, accessible via Telnet and FTP services. This allows remote attackers to gain unauthorized administrative access to the device with full privileges.
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 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Confirm device modelIdentify the GE Healthcare Discovery NM 750b device on your network through network scanning, device inventory, or physical inspection of the medical imaging deviceAffected if The device is a GE Healthcare Discovery NM 750b
-
Check Telnet exposureScan the device or network segment for open Telnet port (TCP 23) using a port scanner like nmap: nmap -p 23 <device-ip>Affected if Telnet service is enabled and port 23 is accessible from the network
-
Check FTP exposureScan the device or network segment for open FTP port (TCP 21) using a port scanner like nmap: nmap -p 21 <device-ip>Affected if FTP service is enabled and port 21 is accessible from the network
-
Verify credential statusLocate the device administration documentation or consult with device administrator to determine whether the default password '2getin' for the 'insite' account has been changedAffected if The default password '2getin' for account 'insite' remains unchanged
You are affected if you have a GE Healthcare Discovery NM 750b device with Telnet or FTP services exposed on the network and the default password '2getin' for the 'insite' account has not been changed.
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 dataImmediately change the default password, disable unused Telnet/FTP services, implement network segmentation to restrict access to the device, and contact GE Healthcare for device-specific security guidance or firmware updates.
- Consultation8.0 h
- Implementation6.0 h
- Testing4.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,400.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7404 — 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-2013-7404 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