CVE-2019-7483
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 · uneditedIn SonicWall SMA100, an unauthenticated Directory Traversal vulnerability in the handleWAFRedirect CGI allows the user to test for the presence of a file on the server.
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 confidenceAn unauthenticated directory traversal vulnerability in the handleWAFRedirect CGI of SonicWall SMA100 appliances allows remote attackers to test for the existence of files on the server file system without authentication.
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< 9.0.0.4CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 as a SonicWall SMA100 applianceLog into the SMA administrative interface or check the device model through the management console or physical labeling. The SMA 100 series includes SMA 200, 210, 400, 410, 500, and 500v appliances.Affected if The device is a SonicWall SMA 100 series appliance running the affected firmware.
-
Determine the installed firmware versionAccess the SMA web interface, navigate to System > Status or About page to view the current firmware version. Alternatively, use the command line and run 'diag sys info' or check /etc/version file if CLI access is available.Affected if The firmware version is lower than 9.0.0.4 (for example, 9.0.0.3, 8.x, or earlier).
-
Verify the handleWAFRedirect CGI endpoint is accessibleSend an HTTP GET request to the handleWAFRedirect endpoint from an external location, for example: curl -k https://<target>/cgi-bin/handleWAFRedirect?st=../../../../etc/passwdAffected if The server responds to requests for the handleWAFRedirect endpoint without requiring authentication, indicating the vulnerable CGI is exposed.
-
Confirm unauthenticated access is possible to the SMA web interfaceAttempt to access the SMA login page from an untrusted/external network without providing credentials. Verify whether the web interface accepts unauthenticated connections on ports 443 or 8443.Affected if The SMA web interface (ports 443/8443) is accessible from untrusted networks without authentication, allowing potential exploitation of the directory traversal flaw.
The environment is affected if any SonicWall SMA 100 series appliance is running firmware version 9.0.0.3 or earlier, with the handleWAFRedirect CGI endpoint exposed to 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.
dbcve · scoped9.0.0.4
Apply the vendor-supplied patch or firmware update from SonicWall to remediate the directory traversal vulnerability in handleWAFRedirect; as a compensating control, restrict external access to the SMA web interface to trusted IP addresses if immediate patching is not feasible.
SMA 100 Firmware 9.0.0.4 or later
- 1. Log into the SMA 100 appliance administrative interface.
- 2. Navigate to System > Firmware or System Administration > Firmware Management.
- 3. Check the current firmware version under Device Status or System Status.
- 4. Download firmware version 9.0.0.4 or later from the official SonicWall support portal (psirt.global.sonicwall.com or my.sonicwall.com).
- 5. In the firmware management section, select the option to Upgrade or Upload firmware.
- 6. Browse to the downloaded firmware file and initiate the upgrade.
- 7. Wait for the upgrade to complete - do not power off the device during this process.
- 8. After the device reboots, verify the new firmware version is 9.0.0.4 or later.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7483 — 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-2019-7483 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