CVE-2019-17445
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 · uneditedAn issue was discovered in Eracent EDA, EPA, EPM, EUA, FLW, and SUM Agent through 10.2.26. The agent executable, when installed for non-root operations (scanning), can be forced to copy files from the filesystem to other locations via Symbolic Link Following.
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 symbolic link following vulnerability in Eracent agent software (versions through 10.2.26) allows an attacker with local access to manipulate the non-root scanning agent into copying files from arbitrary filesystem locations to other destinations. This file manipulation could enable privilege escalation or unauthorized access to sensitive data.
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<= 10.2.26<= 10.2.26<= 10.2.26<= 10.2.26<= 10.2.26<= 10.2.26CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/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 installed Eracent agentsSearch the system for Eracent agent software components. Look for processes or services named Eda, Epa, Epm, Eua, Flw, or Sum, or check common software installation directories for Eracent products.Affected if Any Eracent agent software (Eda, Epa, Epm, Eua, Flw, or Sum) is found on the system
-
Determine Eracent agent versionQuery the installed Eracent agent software for its version information using the software's native version command or check the binary/package version.Affected if The installed version is 10.2.26 or lower
-
Locate agent working directoriesIdentify directories the Eracent agent uses for scanning, temp file handling, or output operations. Check agent configuration files or process working directories.Affected if The agent uses world-writable or group-writable directories for file operations
-
Inspect for suspicious symbolic linksExamine the agent working directories for symbolic links pointing to sensitive system locations or unexpected destinations. Look for symlinks created by non-privileged users.Affected if Symbolic links exist in agent directories that point outside expected scanning targets, especially if created by non-root users
-
Verify file permissions on agent directoriesReview permissions on directories used by the Eracent agent. Check if unauthorized users can create or modify files in these locations.Affected if Agent directories allow write access from non-privileged or untrusted user accounts
The environment is affected if any Eracent agent (Eda, Epa, Epm, Eua, Flw, or Sum) version 10.2.26 or lower is installed and the agent operates on directories accessible to untrusted local users.
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 dataRestrict local access to trusted users only, implement strict file permissions on directories used by the agent, and monitor for suspicious symbolic link creation near agent operations. Upgrading to a patched version once available is recommended.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17445 — 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-17445 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