CVE-2026-28777
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 · uneditedInternational Datacasting Corporation (IDC) SFX2100 Satellite Receiver, trivial password for the `user` (usr) account. A remote unauthenticated attacker can exploit this to gain unauthorized SSH access to the system, while intially dropped into a restricted shell, an attacker can trivially spawn a complete pty to gain an appropriately interactive shell.
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 confidenceThe IDC SFX2100 Satellite Receiver contains a trivial/default password for the 'user' (usr) account, allowing remote unauthenticated attackers to gain SSH access. While initially dropped into a restricted shell, attackers can trivially spawn a full pty to obtain an interactive shell.
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
- 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.
-
Confirm the device model and firmware versionAccess the device management interface or check the device label/web UI for the exact model (Sfx2100 or Datacast SFX2100) and installed firmware versionAffected if The device is a Datacast SFX2100 with any firmware version - all versions are affected
-
Verify if SSH service is enabledCheck the device's management interface, web UI configuration, or system services for SSH server status. On the device console, run: systemctl status sshd or check for port 22 listeningAffected if SSH is enabled and listening - this is required for the vulnerability to be exploitable
-
Determine if the default user account exists with default credentialsCheck /etc/passwd or the device's user management interface for an account named 'user' or 'usr'. Compare the password hash or check if the known default password is still setAffected if The 'user'/'usr' account exists with the default/trivial password still configured - this indicates the device is vulnerable
-
Check network accessibility of SSH portFrom an external host or network segment, verify if port 22/SSH is reachable: nmap -p 22 <device-ip> or telnet <device-ip> 22Affected if SSH port 22 is exposed to untrusted networks or the internet - the device is remotely exploitable
-
Assess whether shell restrictions are properly configuredIf you have access, check if the restricted shell is still in place for the user account, or if pty allocation is unrestricted. Review /etc/shells and user shell configurationAffected if The restricted shell can be trivially bypassed or pty spawning is allowed - attackers can obtain full interactive shell access
The device is affected if it is a Datacast SFX2100 with SSH enabled and the default 'user'/'usr' account still uses the trivial/default password, especially if SSH is accessible from untrusted network segments.
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 for the user account, disable SSH access if not required, and implement network segmentation to restrict access to the device. Check with IDC for firmware updates that may address default credentials.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28777 — 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-2026-28777 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