CVE-2020-7802
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 Synergy Systems & Solutions (SSS) HUSKY RTU 6049-E70, with firmware Versions 5.0 and prior, has an Incorrect Default Permissions (CWE-276) vulnerability. The affected product is vulnerable to insufficient default permissions, which could allow an attacker to view network configurations through SNMP communication. This is a different issue than CVE-2019-16879, CVE-2019-20045, CVE-2019-20046, CVE-2020-7800, and CVE-2020-7801.
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 Synergy Systems & Solutions HUSKY RTU 6049-E70 with firmware versions 5.0 and prior contains incorrect default permissions (CWE-276). The SNMP service has insufficient access controls by default, allowing unauthorized attackers to view network configurations through SNMP communication. This is a baseline permission misconfiguration in the industrial RTU device's default setup.
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<= 5.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 RTU device modelLocate the physical device or network documentation for the Synergy Systems & Solutions HUSKY RTU 6049-E70. Check the device label, management interface, or inventory records to confirm the exact model number.Affected if The environment does not contain a HUSKY RTU 6049-E70 device, then this CVE does not apply.
-
Check the firmware versionAccess the RTU device management interface (web UI, console, or SNMP) and retrieve the firmware version information. Compare against the affected range: version 5.0 and prior.Affected if The installed firmware version is 5.0 or lower.
-
Verify SNMP service statusCheck if the SNMP service is enabled on the RTU device. This can be done by querying SNMP (snmpwalk), checking the device management interface SNMP settings, or reviewing network firewall rules for SNMP ports (UDP 161/162).Affected if SNMP is actively running or configurable on the device.
-
Inspect SNMP community stringsRetrieve the configured SNMP community strings (read community) from the device SNMP configuration or by attempting an SNMP query with common default community names such as 'public', 'private', or vendor defaults.Affected if The community string is set to a default value such as 'public' or was not changed from factory defaults.
-
Assess network accessibility of SNMPDetermine if the SNMP service is exposed to untrusted networks by reviewing firewall rules, VLAN segmentation, or network access control lists. Check if the device management IP is reachable from network segments outside the operational technology (OT) network.Affected if The SNMP service is accessible from network segments outside the trusted operational network or from the enterprise IT network.
You are affected if you have a HUSKY RTU 6049-E70 device running firmware version 5.0 or prior with SNMP enabled and accessible, particularly if SNMP uses default community strings or is exposed beyond the trusted 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 dataReview and restrict SNMP access permissions on the affected RTU device, implement network segmentation to limit SNMP exposure, and contact vendor for patched firmware if available. Verify SNMP community strings are not using default values.
- 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-2020-7802 — 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-2020-7802 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