CVE-2019-7484
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 · uneditedAuthenticated SQL Injection in SonicWall SMA100 allow user to gain read-only access to unauthorized resources using viewcacert CGI script. This vulnerability impacted SMA100 version 9.0.0.3 and earlier.
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 confidenceAuthenticated SQL injection in the viewcacert CGI script of SonicWall SMA100 versions 9.0.0.3 and earlier allows attackers with valid credentials to inject malicious SQL queries, enabling read-only access to unauthorized database resources.
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.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 SMA100 appliance and firmware versionAccess the SMA administrative interface or check the system information page. Navigate to System > Status or similar to view the firmware version. Alternatively, check via CLI using 'get system status' or similar command if SSH access is available.Affected if Firmware version is 9.0.0.3 or earlier (any version up to and including 9.0.0.3)
-
Verify the viewcacert CGI script is presentCheck if the /cgi-bin/viewcacert script exists on the SMA appliance by accessing it via HTTP/HTTPS (e.g., https://<SMA_IP>/cgi-bin/viewcacert). A 404 response indicates the script may not be present or has been removed.Affected if The viewcacert CGI script is accessible and responds (not 404) on the SMA web interface
-
Confirm remote management is enabledVerify that the SMA web interface is accessible from the network segment you are testing. Check under System > Administration > Web Management settings to see if remote access is enabled for the applicable interface.Affected if Remote web management is enabled, exposing the CGI script to network access
-
Check authentication configurationReview the SMA user authentication settings under Users > Local Users or AAA settings. Note that exploitation requires valid credentials, so determine if local user accounts, LDAP, or other authentication sources are configured and active.Affected if Local or external authentication is configured and active, meaning valid credentials could be obtained to exploit the SQL injection
The environment is affected if the SMA100 firmware version is 9.0.0.3 or earlier and the viewcacert CGI script is accessible with authentication enabled.
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 dataUpgrade to a patched SMA100 version or implement proper input validation and parameterized queries in the viewcacert CGI script to remediate the SQL injection vulnerability.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7484 — 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-7484 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