CVE-2019-16519
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 · uneditedESET Cyber Security 6.7.900.0 for macOS allows a local attacker to execute unauthorized commands as root by abusing an undocumented feature in scheduled tasks.
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 confidenceESET Cyber Security 6.7.900.0 for macOS contains a local privilege escalation vulnerability where an undocumented feature in the software's scheduled task mechanism allows an authenticated local attacker to execute arbitrary commands with root privileges. This is a direct root compromise via improper access control on scheduled task functionality.
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.7.900.0<= 6.7.900.0<= 6.7.900.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
- 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.
-
Identify installed ESET productsRun 'ls /Applications | grep -i eset' in Terminal to list installed ESET applications, or check System Preferences > Security & Privacy for ESET-related extensionsAffected if Any ESET Cyber Security, Endpoint Antivirus, or Endpoint Security product is installed
-
Determine installed ESET versionOpen the ESET application and navigate to Help > About, or right-click the app in /Applications and select Get Info to view the version numberAffected if The version number is 6.7.900.0 or lower
-
List ESET scheduled tasksRun 'sudo launchctl list | grep -i eset' or check /Library/LaunchDaemons and /Library/LaunchAgents directories for ESET-related plist filesAffected if ESET scheduled tasks or launch agents exist on the system
-
Check for undocumented or unexpected tasksReview the output from step 3 for any scheduled tasks that accept user-controlled parameters or execute external commands, particularly those running as rootAffected if Any ESET scheduled task runs with elevated privileges and accepts arbitrary command parameters
A system is affected if ESET Cyber Security, Endpoint Antivirus, or Endpoint Security version 6.7.900.0 or lower is installed and ESET scheduled tasks exist that could be manipulated by a local authenticated user to gain root access.
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 patches for ESET Cyber Security when available; until then, restrict local system access to trusted users only and monitor for suspicious scheduled task creation. Consider disabling non-essential ESET scheduled tasks if the product allows.
- Consultation2.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16519 — 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-16519 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