CVE-2019-9533
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 · uneditedThe root password of the Cobham EXPLORER 710 is the same for all versions of firmware up to and including v1.08. This could allow an attacker to reverse-engineer the password from available versions to gain authenticated access to the device.
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 confidenceThe Cobham EXPLORER 710 satellite phone contains a hardcoded root password that is identical across all firmware versions up to and including v1.08. Attackers can extract this static password from publicly available firmware images to gain authenticated root access to the device.
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= 1.07CVSS 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 the firmware version of the Cobham EXPLORER 710Access the device management interface via its web UI or serial console and navigate to the firmware version or system information section. Alternatively, check the boot logs or system information via the command line if SSH/telnet access is available.Affected if The displayed firmware version is 1.07 or any version up to and including v1.08 (e.g., 1.06, 1.05, etc.).
-
Confirm the device has network management interfaces enabledCheck if the EXPLORER 710 has its web management interface, SSH, or telnet service exposed on the network. Use a port scanner or check the device network configuration to see which services are listening.Affected if The device has root access services (SSH/telnet) or the web management interface accessible from the network, making the hardcoded password exploitable remotely or locally on the same network.
-
Verify if default root credentials are in useAttempt to authenticate to the device using the root username with a password that can be extracted from publicly available firmware images for the affected version range. If you have access to the firmware file, extract the shadow or passwd file to confirm the static root password hash.Affected if Authentication succeeds with a root password that matches the hardcoded value found in firmware versions 1.07 or earlier, indicating the device is vulnerable.
The device is affected if it is running Cobham EXPLORER 710 firmware version 1.07 (or any version up to v1.08) and has its management interfaces accessible on the 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 dataUpdate firmware to a version beyond v1.08 that addresses the hardcoded credential issue. If no patched firmware is available, implement network segmentation and restrict access to the device's management interfaces to limit exposure.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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 $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9533 — 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-9533 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