CVE-2019-7487
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 · uneditedInstallation of the SonicOS SSLVPN NACagent 3.5 on the Windows operating system, an autorun value is created does not put the path in quotes, so if a malicious binary by an attacker within the parent path could allow code execution.
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 confidenceThe SonicOS SSLVPN NACagent 3.5 installer creates a Windows autorun registry entry without quoting the executable path. This unquoted path vulnerability allows Windows to misinterpret paths containing spaces, potentially executing malicious binaries placed in parent directories instead of the intended application.
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<= 6.5.3.3= 3.5CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify NACagent 3.5 is installedCheck the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'NACagent' or inspect the program files directory (commonly C:\Program Files\SonicWall\NACagent) for the nacagent.exe file. Use 'wmic product get name,version' or check Add/Remove Programs.Affected if The NACagent version 3.5 is present on the system
-
Locate the autorun registry entryOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run. Look for a value named 'NACagent', 'NAC Agent', or similar SonicWall NAC-related entry.Affected if A registry autorun entry for NACagent exists in the Run key
-
Inspect the executable path for unquoted spacesExamine the data value of the NACagent autorun entry. Identify whether the path to nacagent.exe contains spaces and is not enclosed in quotation marks (e.g., C:\Program Files\SonicWall\NACagent\nacagent.exe instead of "C:\Program Files\SonicWall\NACagent\nacagent.exe").Affected if The executable path contains unquoted spaces, making path injection possible
A user is affected if NACagent version 3.5 is installed and its autorun registry entry contains an unquoted executable path with spaces.
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 dataOrganizations should modify the affected autorun registry entry to enclose the executable path in quotes, ensuring proper path resolution and preventing arbitrary code execution via path injection.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7487 — 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-7487 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