CVE-2015-7770
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 · uneditedDell SonicWall TotalSecure TZ 100 devices with firmware before 5.9.1.0-22o allow remote attackers to cause a denial of service via a crafted packet.
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 confidenceA denial of service vulnerability exists in Dell SonicWall TotalSecure TZ 100 firewall devices running firmware versions prior to 5.9.1.0-22o. The flaw allows remote, unauthenticated attackers to send specially crafted packets to the device, causing it to become unavailable.
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.9.1.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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 device modelAccess the SonicWall administrative interface or CLI and verify the hardware model is Dell SonicWall TotalSecure TZ 100. This can typically be found on the System Status page or using the 'show system info' command.Affected if The device is a Dell SonicWall TZ 100 firewall.
-
Identify installed firmware versionLocate the firmware version in the administrative web interface under System Status or Device > Status, or use the CLI command 'show version' or 'sysinfo'. Note the full version string including any build numbers.Affected if The device is a TZ 100 and the firmware version cannot be determined or is not visible.
-
Compare firmware against vulnerable rangeTake the installed firmware version string (for example: 5.9.0.0, 5.9.1.0-21o, etc.) and compare it to the fixed version 5.9.1.0-22o. Any version less than 5.9.1.0-22o is in the vulnerable range.Affected if The installed firmware version is 5.9.1.0 or any earlier version (versions ending in -21o, -20o, etc.), or any 5.8.x or earlier release.
-
Verify if remote management is enabledCheck the firewall configuration in the administrative interface under Management > Settings or Network > Interfaces. Look for whether the WAN or external interfaces have management services (HTTP, HTTPS, SSH) enabled for remote access.Affected if Remote management is enabled on WAN interfaces and the firmware version is below 5.9.1.0-22o, the device is remotely exploitable without authentication.
If the device is a Dell SonicWall TZ 100 running firmware version 5.9.1.0 or any earlier version (anything below 5.9.1.0-22o), the environment is affected by this CVE.
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 the device firmware to version 5.9.1.0-22o or later. Prior to the update, schedule a maintenance window and verify backup configurations are available.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7770 — 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-2015-7770 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