dbcve.org
Sfx2100 FirmwareOperating system · Datacast

CVE-2026-28775

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
An unauthenticated Remote Code Execution (RCE) vulnerability exists in the SNMP service of International Datacasting Corporation (IDC) SFX Series SuperFlex SatelliteReceiver. The deployment insecurely provisions the `private` SNMP community string with read/write access by default. Because the SNMP agent runs as root, an unauthenticated remote attacker can utilize `NET-SNMP-EXTEND-MIB` directives, abusing the fact that the system runs a vulnerable version of net-snmp pre 5.8, to execute arbitrary operating system commands with root privileges.

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 confidence

The IDC SFX Series SuperFlex SatelliteReceiver ships with a default 'private' SNMP community string configured with read/write access. Since the SNMP agent runs as root and the underlying net-snmp version is pre-5.8, an unauthenticated attacker can leverage NET-SNMP-EXTEND-MIB directives to execute arbitrary operating system commands with root privileges.

MitigationChange the default 'private' SNMP community string to a strong, unique value and restrict SNMP access by IP or disable the service if unused. If net-snmp cannot be upgraded to 5.8+, consider network segmentation to limit SNMP exposure.

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
Sfx2100 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Query the device via SNMP using system descriptors (like snmpwalk -v2c -c public <device_ip> sysDescr) or check the device web interface/network configuration for model identification
    Affected if The device is a Datacast Sfx2100 or IDC SFX Series SuperFlex SatelliteReceiver
  2. Confirm SNMP service is running
    Perform an SNMP scan of the device IP using 'snmpwalk -v2c -c public <device_ip> system' or port scan for UDP 161
    Affected if SNMP responds to queries, indicating the service is enabled and accessible on the network
  3. Verify community string configuration
    Query the device using the 'private' community string: 'snmpget -v2c -c private <device_ip> sysLocation' or 'snmpwalk -v2c -c private <device_ip>'. Also check if 'public' and 'private' both return valid responses
    Affected if The default 'private' community string is accepted and returns valid SNMP data with read/write access
  4. Check net-snmp version
    If accessible via SSH or console, run 'snmpd -v' or check the net-snmp package version on the device firmware. Alternatively, query SNMPv2-MIB::snmpVersion via 'snmpget -v2c -c private <device_ip> snmpVersion.0' if exposed
    Affected if The net-snmp version is 5.8 or earlier, making the NET-SNMP-EXTEND-MIB exploitation vector viable
  5. Test for NET-SNMP-EXTEND-MIB command execution
    Query the NET-SNMP-EXTEND-MIB: 'snmpwalk -v2c -c private <device_ip> nsExtend' or 'snmpset' to create a test extend entry
    Affected if The NET-SNMP-EXTEND-MIB tree is accessible and allows creating or viewing extend entries, confirming arbitrary command execution is possible with root privileges

A defender is affected if they have a Datacast Sfx2100 device with SNMP enabled and the default 'private' community string still configured, especially if net-snmp version is 5.8 or earlier.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Change the default 'private' SNMP community string to a strong, unique value and restrict SNMP access by IP or disable the service if unused. If net-snmp cannot be upgraded to 5.8+, consider network segmentation to limit SNMP exposure.

Fix this in Sfx2100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28775 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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