CVE-2020-7801
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 Exposure of Sensitive Information to an Unauthorized Actor (CWE-200) vulnerability. The affected product is vulnerable to information exposure over the SNMP protocol. This is a different issue than CVE-2019-16879, CVE-2019-20045, CVE-2019-20046, CVE-2020-7800, and CVE-2020-7802.
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 an information disclosure vulnerability (CWE-200) where sensitive information is exposed over the SNMP protocol to unauthorized actors. This affects the confidentiality aspect of the device, potentially leaking configuration data, system details, or other sensitive operational information through SNMP queries.
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 device modelCheck the physical device label or access the device's web interface or console to confirm the model is HUSKY RTU 6049-E70Affected if The device is a HUSKY RTU 6049-E70
-
Check the firmware versionAccess the device's administrative interface or use SNMP GET on sysDescr.0 (1.3.6.1.2.1.1.1.0) to retrieve the firmware version. Compare it to the affected range: firmware <= 5.0Affected if Firmware version is 5.0 or any version prior to 5.0
-
Verify SNMP is enabledSend an SNMP GET request to the device on UDP port 161 (e.g., snmpget -v2c -c public <device_ip> sysDescr.0). A successful response indicates SNMP is activeAffected if SNMP queries return a valid response, confirming SNMP is enabled and accessible
-
Check SNMP access exposureDetermine if the device SNMP service is reachable from untrusted networks by testing UDP port 161 connectivity from external hosts or reviewing firewall rulesAffected if SNMP port 161 is accessible from networks outside the trusted management segment
The environment is affected if the device is a HUSKY RTU 6049-E70 running firmware version 5.0 or prior with SNMP enabled and accessible from untrusted networks.
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 dataApply vendor-supplied firmware updates if available; otherwise, restrict SNMP access through network segmentation, firewall rules, or VLAN isolation, and disable SNMPv1/v2c in favor of SNMPv3 with authentication and encryption.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.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 $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7801 — 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-7801 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